SOMEONE FORGOT TO TURN OFF CAPS LOCK

rejected because no random tests.

no random tests while they are implemented in all other languages. Rejected.

APPROVED SOME TIME AGO

https://www.codewars.com/kumite/5ef514f6a740d0001a25e2e6?sel=5f0e166343793800327ead58 hope, I've done it right way

Merge conflicts can only be resolved in forks, otherwise it doesn't work.

updated

Merge conflict. Fork and update the description.

renamed test groups

describe "All Negative tests" do
  it "tests" do
    Test.assert_equals(quadratic(0, -1), test(0, -1))

0 isn't negative.

I didn't tune the tests here, actually. For this time, it's all on the author's back... ;)

I would say you should go the way of making language versions proportional in terms of time. If java performance tests take X% of allowed time, put as many test cases in Ruby so they will also take X% of available time.

Usually it's enough for performance tests to run ~6s or so, so user has some margin and they can focus on general approach rather than microoptimisations. I have no idea how intensive java tests are, but knowing B4B I'd guess X is nothing like 50%, tho :) If it would mean that Ruby has 100x fewer tests than Java, then it's OK. Anyway, no one would expect more from Ruby, right? ;)

that's not enough yes. Considering the number of tests in Java, less than 5000-6000 (edit, maybe a bit less...?) in Ruby would end up in a joke. Especially considering the reference solution solves those 40000 tests in "no time".

The only way to proceed, here, would be to translate an efficient solution (knowing there are no antipatterns for performances that are specific to ruby), then tune the tests. But clearly, this could be a pain...

Really wanna make a ruby translation for this kata, but I don't sure - what should be perfomance expectations? I mean, 40k tests for Ruby for this kata is impossible to be done in 12 seconds. Is there some rules or way to calculate fair expectations? I spend hours solving Marple puzzles on iPad, algorothmized all ways to reduce board possible values, then refactored my solution, but best perfomance I could reach for now - about 400 tests per 12 seconds (in codewars environment). It's much better than any brute force solution written in Ruby, but comparing with Java 40k tests - 400 looks like nothing.

Done. Thank you!