C# Translation

Fixed tests below should be added to all languages

• you yo ou u yu

• ou

• yo

• u

• you

First Test Case "May 3" is broken. Convey different meanings. "May 3" and "May 13"

Test.assertEquals(getVillainName(new Date("May 3")), "The Despicable Raisin", "Expected result: The Despicable Raisin; Your result: "+getVillainName(new Date("May 13")) );

To fix this from the testing side, whoever set up the tests should be using == (value comparison) instead of is (reference comparison) to compare strings. If this is not a deliberate decision on their part, it's a mistake in the test setup.

Python tests check for reference equality of coupon codes, which seems to be wrong. Reference solution will, and valid solutions are expected to, reject valid entered_code which happen to not be interned to the same instance as entered_code, even if their values are equal.

I think that value equality of coupon codes should be preferred, but if not, then description has to specify that "valid code" is expected to be equal to an expected code by reference, and not value.

Prolog translation requires a spec of the date. I have to assume what itrepresents from an example test case

The description example must be included in sample tests for all languages.

JS:

• No sample test
• No random test
• Outdated Node version.

You might want to rename the title to Easy Email Validation to prevent people from assuming the kata to be a proper email validation.

I've written a Racket translation.

Ruby 3.0 should be enabled, read this to learn how to do it

Please organize the structure of test fixture as following (although it has been mentioned in the attached link, I'm repeated here again)

describe "<This message should describe the categories of test groups inside this block>" do
  it "<A short message describing this test group>" do
    expect(...).to eq(...) #Assertions
    #Or Test.assert_equals(user_response, reference_response)
  end
end

Ruby 3.0 should be enabled, see this to learn how to do it

Please organize the structure of test fixture as following (although it has been mentioned in the attached link, I'm repeated here again)

describe "<This message should describe the categories of test groups inside this block>" do
  it "<A short message describing this test group>" do
    expect(...).to eq(...) #Assertions
    #Or Test.assert_equals(user_response, reference_response)
  end
end

Ruby 3.0 should be enabled.

• No sample tests in JS

• assert.deepEqual should be used

• Node 18. (mocha + chai should be enabled)

• Several fixed tests are executed after random tests, which is very erroneous since the point of fixed test is to help users in debugging and identifying edge cases, if any.

• Assertion messages are extremely unhelpful