have a look at my solution

I was wondering which anti-exploit measures you were referring to as ridiculous?
Each was added to counteract an exploit that my original version failed to detect.

no longer applicable

This kata has some truely ridiculous anti-exploit measures in place. Here's the next solution that passes: https://www.codewars.com/kata/reviews/655227c379b2e50001239f76/groups/6560a5e63d749b0001e9e8e0

I have updated the testing so the solutions you pointed out correctly fail

I have updated the testing so your solution correctly fails

Yes, the test code was the same (one of many mistakes)

To clarify, in beta and live kata:

1. If you have not solved the kata you can only see the sample example Test Cases. The full Test Cases are hidden
2. Once the kata has been solved, you can see the full Test Cases

I was not aware of this and assumed to avoid re-training with full test case knowledge in mind that the full test cases would always be hidden

As highlighted by your submissions I will need to take this into account

Thanks for the pointers. Can I ask if the full test suite code is visible to you? I am unclear how much is visible in a beta kata and if the same visibility rules apply if a kata is accepted.

Thank you for the feedback. You are correct. It should not pass.
I am still new to authoring and this is a valuable learning experience!
I will work on a fix.

I assume this shouldn't pass.

This too:

https://www.codewars.com/kata/reviews/655227c379b2e50001239f76/groups/655234d07803a600015e57a6

This is what happens when test code are written with poor code quality.

These solutions shouldn't be allowed:

• https://www.codewars.com/kata/reviews/655227c379b2e50001239f76/groups/655229a99e42ae0001fe5a68
• https://www.codewars.com/kata/reviews/655227c379b2e50001239f76/groups/6552330b3c266b0001271139

The intention was to not give a final target code length to make the challenge interesting

As the coder submits their one-liners, the target would be beaten and the next one given ("I've finally done it... oh no, more to do!")

The first target is 128 and it steps down 16 each time the coder achieves this (until 48)

It is intended to mimic the challenge of code golf in that you usually have no fixed target but must try and reduce it further

I have updated the description detailing this

Thanks for the suggestions.

The (byteToMirror, byteMirrored) is actually the accidentally the wrong way round but as the mirroring works both ways it doesn't make a difference.

I also intended to replace the long constant array with my final function but forgot. I have now done this

Both of your suggestions have now been implemented

Also, please split that tests array over multiple lines so syntax highlighting keeps working - it doesn't with lines over a certain length.

I don't know the maximum length it considers reasonable, sorry. No more than a single screen width at 1980 pixels seems humanly reasonable, and prevents having to scroll as well.