Type of questions is number at some basic tests.It was surprised as for me.

(JS) The function should return the test's maximum possible score as an integer. However we're in may cases given non integer values and tests expect float number.

python translation:

https://www.codewars.com/kumite/5ea57612097e7900235285b1?sel=5ea57612097e7900235285b1

Not an issue. The result can be calculated exactly.

While doing this kata in Ruby, I got this error in the test results:

(Inputs were: {:RANDOMAGAIN=>68950.47331035147, :RANDOMFIRST=>111.42596988890763, :another=>5}, ['RANDOMAGAIN', 'another'])

Expected: 138022.37259059187, instead got: 138022.37259059184

That's a bit too precise, don't you think?

Strangely, I looked at the fork and it was still using string instead of object. Looking at the diff, I could only see a small change to the description. Ordinarily, I leave it up to the author/translator, but I went ahead and made the fix myself, though, and it seems to have stuck this time, so I'm closing my own issue.

Hmm, I thought this was resolved.

Oh well, it should get resolved when the author approves this fork, which is a clone of the appropriate fixes to the sample tests.

There's still a problem with the C# translation. The test cases now use objects while the sample tests still use strings. I was able to satisfy both by writing mine using a generic, but that may not be a 7-Kyu technique...it would be better to either stick to using objects everywhere or switch to strings, but not both.

Thanks for letting me know. Someone else wrote the Ruby translation, and last time I checked I wasn't able to edit it myself. Do you know if that's possible? This is my first kata. I appreciate your help!

There is a problem with the tests for Ruby translation. The first argument's inputs look like: {"a": 1, "b": 14}. This is valid syntax for a javascript object, but not valid syntax for a ruby hash, which looks more like {"a"=> 1, "b"=> 14} or {a: 1, b: 14}.

Thank you for the feedback. You're absolutely correct that I made a mistake in saying that the answer should be an integer. My apologies. I've corrected the question statement.

I agree with you about the fact that some of the test cases aren't realistic, given the fact that the kata is supposed to be questions on a test, but these tests were suggested by previous users to help test the kata more thoroughly.

I'm not sure what exactly you mean by a hacky string converstion; I did not encounter that issue in my solution. I will gladly make additional changes as appropriate if you have other specific suggestions.

Thanks for your patience. This is my first kata to author, and I'm still learning, as you can see. I appreciate your feedback.

Thanks for the feedback. I went ahead and made the statement that the questions are case sensitive its own line. I hope this helps future coders!

The hardest part was realizing that the questions were case sensitive, eventhough I was sure I had read the full specs. :|

It's a good teaching tool in that people will learn to really understand the specs, but the rating will probably be lower than if "The questions are case sensitive" had its own line in the specs or was more obvious some other way.

It looks like Souzooka was able to make this change. Let me know if you're not seeing it. Thank you!