Java:

• Asking users to declare multiple function signatures to match different GENERIC types is riduclous and out of scope of a 7kyu (It is also neither mentioned in the description nor clearly stated in the initial solution setup). Users can only know what signature to write based on the error feedback from tests which is not a good practice ...

Strongly suggest to revamp the test suite to just use String[] which uses natural ordering as the sorting criteria (lexicographically ordering) , same as C# , TS and other strongly typed languages

for good practice, the description should mention that a stable sort is expected

better instructions should be,

with descending order ;

  * dates,   2 > 1 
  * letters, A > Z 

C translation, somewhat patched up, moved from duplicate kata JavaScript Array Filter. Please review.

Randomized testing in Haskell (and maybe other languages) can result in the following:

Falsified (after 16 tests and 13 shrinks):
  ["`","a"]

The description lacks enough detail to determine sorting behavior between letters and characters whose ASCII value falls between the upper and lowercase letter ranges: [\]^_`

C Translation

Fortran Translation

error: could not find `Cargo.toml` in `/workspace` or any parent directory, issue raised when try to test the code in Rust

For Java's actual tests the following warning comes up:

Apr 14, 2023 7:57:51 AM org.junit.jupiter.engine.discovery.MethodSelectorResolver resolve
WARNING: Possible configuration error: method [void SolutionTest.random_tests()] resulted in multiple TestDescriptors [org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor, org.junit.jupiter.engine.descriptor.TestTemplateTestDescriptor]. This is typically the result of annotating a method with multiple competing annotations such as @Test, @RepeatedTest, @ParameterizedTest, @TestFactory, etc.

Bro... I'm sure those kotlin random test got something wrong. In some cases it required more solutions but when I look close to the list of cards, none of them match anymore.

( definitely JS, possibly Ruby, not Kotlin )

Missing random tests

Example tests show

# From Ruby 3.0, RSpec is used under the hood.
# See https://rspec.info/
# Defaults to the global `describe` for backwards compatibility, but `RSpec.desribe` works as well.
describe "Example" do
  it "should return the sum" do
    expect(add(1, 1)).to eq(2)
    # The following is still supported, but new tests should now use them.
    # Test.assert_equals(add(1, 1), 2)
  end
end

Seen this in other ruby katas before. Seems to be a CW issue. Don't know when the last successful submittion was, but the last comment was 3 years ago.

I have a feeling this kata is broken. Unfortunately I can't see when this was successfully solved last time but having an unresolved issue for 4 years and only one comment 2 years ago are some indicators...

The example test I get tests an add() function, which has nothing to do with the kata. When resetting the kata, the example test is empty. I tried writing my own tests and got a solution. Unfortunately I receive this when clicking attempt:

main.rb:26:in `eval': no implicit conversion of Symbol into Integer (TypeError)
	from main.rb:8:in `block in get_value'
	from main.rb:7:in `each'
	from main.rb:7:in `get_value'
	from (eval):1:in `test_equal'
	from main.rb:26:in `eval'
	from main.rb:26:in `test_equal'
	from main.rb:35:in `<main>'

All tests up to that went through. Also tried debugging the input values when the function gets called, but I do not get any values indicating another failing test.

The python translation's random tests can test with zeros, but don't always, allowing solutions that don't handle zero correctly to pass. Zero inputs should be tested explicitly in the basic test cases. Fix