Description is too vague. You don't really know what you're trying to solve until you click attempt and can view the test cases

( 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 ).

The description is not accurate in defining correct names, and in defining the input.

A name is a uppercase letter followed by one or more lowercase letters. The input is not necessarily composed of valid names ( this is the whole point of the kata ).

String, word, name, input and yourID are sprawling all over. Specifications should be correct, complete, and consistent; what names you call things matters.

The meaning may be clear enough to you, it really is not to me.

Fixed. That solution no longer passes.

The grammar is terrible yes, but the meaning is clear enough. There are literally specs at the bottom.

Fixed in CS as well

Fixed. Holy were those random tests bad.

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.

Many issues in JavaScript:

• No fixed tests in full test suite
• Random tests use global variables
• Random tests potentially generate only 1 test
• Random tests potentially generate infinite tests and times out (or exceeds buffer size)
• Random tests print to console
• Tests do not follow general kata coding guidelines and are hard to read
• Node 18 should be enabled
• Chai should be used for assertions

Refer to the top-voted solutions.

Approved

python new test framework is required. updated in this fork

Approved