or not.... sorry unemployed person here

Yep...it really should have been corrected by now.

Came here to say this. I could not figure out why my test was failing. Then I just thought about it for a second. But, following the logic, it does fail.

It makes sense that if a new Song object is instantiated that it would start with no listeners yet.

The description should clarify that a speed of 30 or more Kph above the speed limit results in the addition of a $500 fine. As it reads now it indicates that a speed in excess of 30 Kph above the speed limit (but not at 30) results in the added fine. If you follow the instructions as they are right now your tests will fail.

Loved this Kata! Easy on the coding and a thinker on the math.

Glad to see some exception handling in here for practice! Nice touch. On that note, consider changing the description to exclude "n and m are natural numbers (positive integers)" because that informs the coder what to expect and what not to expect. Even though it is suggested in the example, it is contradictory in the description. Really liked seeing this one, though. Giving this a "Very"! :)

Forgive me for giving half a care about the content on this site.

You are super smart, we get it

The reference solution in C# expected half-up rounding. In other languages, it just expects the default rounding mode of the language. Though, most sunmitted solutions in C# use the default rounding too, this particular feature of C# test is not justified. Unless I miss something, I think it just be aligned on other languages.

Apparently that is the case in Java. lol There was a nice explanation in the comments before. I guess the admins deleted it but it did explain nulls for this kata really well.

null doesn't have property .length

Not sure why but this solution didn't work for me. This is what I had and the test result failed saying something like "for input 10011010010" and nothing else. Copy/paste of the above code did the same thing. ???

For Java the "expected" and "but was" are reversed.

sampleTest
Log
1
2
3
4
5
expected: but was: