Java: missing random tests. Also negative numbers are accepted as two's complement OR with - sign while only the latter should be accepted according to description.

Ruby 3.0 should be enabled.

Ruby 3.0 should be enabled.

Ruby 3.0 should be enabled.

Ruby 3.0 should be enabled.

In JS, the class attributes should be in camel case ( e.firstName and not e.FirstName ).

The description should make clear what is the expected order of the returned array. It's not obvious (order of the first occurrence, second, last?).
Edit: After solving the kata, I guess it's the second occurrence that's used (it's not clear if there may be more than two anyhow).

The punctuation and casing of words (uppercase, lowercase) should not matter for the purpose of this kata

And how should they be handled then?

(JS) The kata asks to remove duplicates from the original array, which can only be done by pass-by-reference, which, unless I'm mistaken, is not possible for arrays. Am I missing something?

'just wanted to make py3 available for the kata, but I discovered that the whole testing process was actually totally flawed... x(

I updated the python test suite by:

• adding two edge cases
• changing the reference solution which was wrong
• changing totally the process of the tests/assertions to actually match the requirements.
• converting the class to namedtuple to avoid some kind of cheats (note: I didn't change the description on purpose, considering the goal is to use the getters)

JS and ruby need to be updated yet...

As mentioned below, this kata is plagued by floating point errors.

You should compare floating point values with a threshold.

description should be updated about what is actually considered a word or separated words: X-RAY is only one. That matters to know that, depending on the approach the warrior choose.

lkspencer, could you please provide test_7(BinaryCalculatorTest) code for Java? I passed 9 tests and failed with this test only.

First of all, I really like this kata. Unfortunately I can't pass it right now in ruby because the random tests for the getvoltage/getresistance methods vary slightly from my solutions at or around the 15th decimal place (a few quadrillionths). That is one precise BBQ! I think the rounding error fix computerguy103 pointed out needs to be implemented in the ruby version so it limits the verification of random tests to 5 decimal places.