Fork with following changes:

• Scrutinized test with order and name annotations (Removed original logs)

• Added more useful assertion messages

• Updated to Java 17.0

• Made initial solution setup compile

• Made random tests generation range smaller to not always generate drink whisky

Fork which made following changes:

• Made initial solution class name -> PascalCase and ensured it compiled

• Made reference solution different from author's solutions

• Scrutinized tests with order and name display annotations

• Organized display of assertion messages

• Made array size randomized instead of capped at length of 5 for each odd and even values

• Enabled Java 17.0

I tried to approve but I'm getting Description cannot be approved, recent changes from related record must be merged first.

Should be fixed.

Perhaps this would have been better as a suggestion, and not an issue. I still believe it is important for the kata description to accurately lay out what is expected. I like having to puzzle out solutions too, but this is a case of being asked to solve the wrong thing.

System.out.println("Random tests."); is unnecessary, there already is a test group header.

Hello All,

I can see that the method names are now OK and tests seem to be fine.

Can this kata be approved?

Thanks

Then the Kata is not clear on that. It mentions nothing about being able to shuffle people around. When most people think a line, they think first to last, one after the other.

The data type of the characteristics column is Text.
column_name data_type
characteristics text

So when you try to select the distinct value of that column, the whole text is compared against the other rows.

id name characteristics
1 Cyril big, smelly
2 Tiny small, stinky, smelly

So give the above, it will check the "big, smelly" against "small, stinky, smelly" which are two different strings, even though the second one has a characteristic that the first one has.

"If you get more than 3, you will be kicked out, for being too smart". There is something in SQL that could be benefical for making sure you don't get kicked out for being too smart.

So I think you are incorrect in how you are generating the numbers.

Given y = (x * 2 +1 ), you aren't looking to plug n in there, as x is what is in u.

This sentence might help clear up the issue "1 gives 3 and 4, then 3 gives 7 and 10, 4 gives 9 and 13, then 7 gives 15 and 22 and so on..."

So you start with 1, y will equal 1 * 2 + 1 = 3, z =4. So now it looks like [1,3,4] The next step is moving to the next item in the sequence. So you do the same y = 3 * 2 + 1 = 7 and z = 10 and so on.
So you aren't plugging into the y or z formula but are using the numbers in the sequence.

The assert tests could be more verbose on what is being tested

Method names should use camelCase in Java.