( JS, possibly others )

The Example tests seem to warn for names with accented vowels in them. This then doesn't happen in Submit tests.

Either remove accented letters from the kata completely, or test consistently between example and submit tests ( ie, add fixed and random tests expecting both true and false for names with accented vowels ).

Description promises us a "String" that is specified to be a first name, either hyphenated or not. So return true should solve the kata.

That is, supposing yourID is that string, in which case it is horribly misnamed.

I don't suppose things work that way, but it is unclear how things are supposed to work.

Can we add new test cases for Lua to assert that NIL and Empty String ("") are also validated?
Because I ran through some solutions for Lua and they work only for valid input and don't work for NIL values.
Or at least remove the requirement from description

Ruby 3.0 should be enabled.

Ruby 3.0 should be enabled.

Random test cases expected false when the input string is valid:
'bkngaojk.gif' - expected false, got true
'jrgigirh.alac' - expected false, got true
and so on...

Am I missing something or are these actually invalid inputs?

You could possibly list all the possible accentuated characters that may appear in the tests in your Kata description.

Add a test to cover the proper existence of a ., e.g.

Test.expect(!'filemp3'.isAudio(), 'File name and extension should be separated by a dot (.) !');