@DanielRomanMartinez, it's because I commented out part of my solution that ckecks for double spaces.

The description tells we must also check for double spaces in the middle of the string, not only at start and end of it

But part of my comment in my solution isn't correct, I just figured out that sample test works fine since it hasn't double spaces

Dart translation random tests must be fixed.

Check up strings with double spaces.

If you think it might be a duplicate, it probably is.

Encodings of inputs or outputs don't really matter; it's the underlying task that has to be novel. ( If encoding the input or output is a kata in itself, you're not doing one thing. )

Having a novel idea is hard. :/

I knew it. Thought it is different enough though

Anyways I'm good with it, just will keep trying

Thank you, I did read the tests. But now I see I need to inspect them better.

I mostly like ones with detailed descriptions.

One more piece of bad news.

Duplicate.

This is fine.

Default assertion fail message includes actual and expected value, and it's generally accepted that if you want to know the input, you can just print it, So you don't really need a custom message at all. But it's nice to have.

I made some changes. Is it good or should test descriptions be done more specific?

A lot of this stuff is in the docs. Maybe not all of it, but a lot.

Did you read tests for kata you solved? There's a lot to be learned there as well.

assert.strictEqual

While you're at it, set Node version 12. No need to languish in legacy versions.

this is my first Kata

Yeah, I already knew that. Unfortunately, you're not the first new kata author to make the same mistakes.