So? This isn't school. People are here to learn and get better. If they're writing their code as switch statements for particular tests, that's their loss. Real test-driven development involves being able to see the tests that you're writing code for.
I updated the description and test cases to no longer expect floating point numbers. This invalidates all of the existing solutions but at least this should resolve the issue for those new to taking the kata.
There was a bug in the initial solution, I have fixed it.
yes,i get it too.
Simply change the regexp so it can't be "fooled".
So? This isn't school. People are here to learn and get better. If they're writing their code as switch statements for particular tests, that's their loss. Real test-driven development involves being able to see the tests that you're writing code for.
The problem with this is that it gives away the test cases.
Test cases are good, your combinations are not properly ordered. Read the description again.
I updated the description and test cases to no longer expect floating point numbers. This invalidates all of the existing solutions but at least this should resolve the issue for those new to taking the kata.
Does the new description make sense?
Implementation specific percentages.... :(