Uneinheitliche Syntax in deinem Mapping triggert schon bissl xD

Works like a charm. Thanks!

Hello, I wrote some describe and it-headers but two issues occoured. I thought you might know something about them :/

• With Node v10.x long arrays in errors don't get displayed properly. It just displays expected [ array(4) ] to deeply equal [ array(4) ] so the user can't see the difference. Is there a solution except transforming everything into strings?

• With older node versions, arrays in errors are displayed better. But I noticed that below all the proper test outputs an unhandled error field is always displayed. E.g. Unhandled rejection TestError: Expected: ['#ffffff'], instead got: []. I am not shure why. I thought I handle all the errors properly.

Thanks for the fix. It should now work like the solution in your fork.

@JohanWiltink, thanks for letting me hijack your solution btw :/

@Blind4Basics, random tests are now executed after fixed tests.

@Unnamed, issue should be resolved now.

Thanks for testing. I originally didn't intend to allow arrays with duplicate entries as input, so I forgot to consider that case.
It is fixed now. I also added an array with duplicate entries to example tests and static tests.

@JohanWiltink,
yes, issues should be resolved now.

@JohanWiltink, after you said your sorting should not have made a mistake like this, I checked once again and found out you are 100% right...
In my random tests I swichted the arguments of Test.assertDeepEquals around so the "expected"-value was your (correct) value, while the "actual"-value was my own (incorrect) value.
Stupid mistakes but I will only make them once, hopefully.

Thanks for the feedback. You are right. Will fix asap.

As you noticed, auto generated tests don't produce this scenario very often. Will change too.

Hey, thanks a lot for the feedback. If you are interested about what the problem was:
Your algorithm doesn't work correctly if more than two pairs in the returned array have the same first color.
E.g. your return array sometimes has entries like [(...) ['#85613A', '#8B563B'], ['#85613A', '#8F4F36'], ['#85613A', '#8B6930'] (...)] which isn't correctly ordered, because '#8F4F36' is bigger than '#8B6930'.
Funny enough, my own solution also sometimes doesn't sort correctly in these cases. Will fix asap.

Hello, thanks for the feedback. What exactly do you mean by that?
I thought it should be Test.assertDeepEquals(actualValue, expectedValue) which I wrote.

Thanks for the feedback. I am putting the kata on hold until I have reworked it properly, which will be soon.