Thank you so much!

I copied over what you wrote and continued the rest. I didn't understand that this is what you wanted at first.

Sorry for the inconveniece. Please let me know if this is good.

Hello, they should not be there. Removed.

approved

I fixed the pawn captures. I don't think any other moves are illegal, but please check me on that. I'm most likely wrong. Thanks for the feedback though!

It seems I forgot to remove those lines of code to print out the random tests. I was just doing that for testing purposes.

I'll make sure to fix the pawn captures as well. Thanks!

Could you tell that this was my first kata? I didn't know much about how to do these things.

After a while, people stopped doing this kata, and I didn't remember to fix these things.

Thank you for making this suggestion. I followed all of your suggestions and I fixed the issues.

I also included en passant, it should be in the description. Thanks a lot!

Done, thanks for the tip.

approved

is there a certain type of tree that would make it fail consistently ?

can you provide link(s) to such solutions ?

(I'm not sure if the random tests are really needed, given the number of fixed tests, which would be very tedious to hardcode.)

Hardcoding past any suite of fixed tests is nothing more than a regex replace of the reporter output. Random tests are always needed.

approved by someone

Performance constraints are different, and the identifyable parts are also different enough to make these two different kata's.

Thanks a lot! Good stuff. Approved.

In alot of cases this is true

But there are some scenarios where having a wall instead of a pawn changes the outcome