This is missing a whole lot of cases, no?

Here's a few:

"The Giggling Sisters (10000) dir. Bob Bob, Bob Bobbet" <- The _ Sisters in wrong location, and surname Bob, followed by a Bob as first name
"The Giggling Sisters (10000) dir. Your Mom, Second Mom, and Also Dad" <- False? Because not exactly two
"The Giggling Sisters (10000) dir. The Sisters, Those Brothers" <- starts with The, contains brothers/sisters, ends with Brothers
"The Giggling Sisters (10000) dir. A B, C B (20000) dir. The Sisters, Those Brothers" <- Weird title. permissible?
"The Giggling Sisters (10000) dir. The A Sisters, The A Sisters" <- A Sisters mentioned twice, thus should be False

Description mentions "Several guys" but I don't see the word "and" used anywhere in the test code at a glance. That'll cause people to write code for this - except it.. isn't part of the task?

• Sample tests are missing the imports for test framework and solutions

• Description does not mention whether a middle name will be expected, should have mentioned what constitutes a name and its form, which in this case is ${firstname} ${lastname} only

• Also these tasks have been done to death (Similar ones listed below) --> Basic string parsing with direct solution giveaway just by reading the description !

  1

  2

  3

  4

You know what else is free too? --> Authoring katas on CW in any spoken language of your choice (The rules prohibit this but not the system ^^)

The whole design of this kata is flawed. Mixing different data type for expected output is a bad practice, let alone needing to explicitly handle the case when only 1 combination is found!

As of 21/1/2025, there are a total of 323 submissions, so revamp of tests to expect only an array of arrays / a list of lists can still be done with minimal tradeoff with all solutions being invalidated ! (This also adds the compatibility of the kata to be translated across strongly typed languages)

• If the function receives an empty array will output an specific alert:

  Why not just return [] for this case? Since an empty array literally represents nothing to process in the first place !!!

• If there are no combinations with sum equals to 0, the function will output an alerting message.

  Why not just return [[]] for this case ? Since an array consistng of only an empty array represents after processing the array, no combination was found

• Description does not mention we need to just return the first combination, not the entire array. Though the first example implies this, it is no where stated clearly in written words...

• OTOH, the explicit handling of 1 combination mentioned above increases the number of data types for the expected output -> an array. So, such requirement should not be there in the first place !

• Node 18. should be enabled

• Test.expect should be aborted

• Assertions that do not test anything should be removed, like this one:

  Test.expect("randomCase", "Random case function expected");

• Description should be language-agnostic

• Write a function that will randomly upper and lower characters in a string

  should be

  Write a function that will randomly convert characters in a string to their lowercased and uppercased form

• JS Node 18. should be enabled

• Golfed reference solution should be ungolfed

JS Node 18. should be enabled

Description has unnecessary <p> and <select> tag, should be removed.

Node 18. should be enabled

Description should be language-agnostic

done

The input given can be null, so you should explicitly handle that first before filtering the array

It simply means to find the unique combination with a size of m whereby m is the lowest frequency of an element in the array of digits.

suggestion on how to solve it != kata suggestion