Not explained properly. Very simple problem but just because not explained properly creates too much ambiguity. You get confused in where you have the list of generated names.

Explanation For Beginners:
You have 4 inputs:
--- 2 objects provided by default (in background) from which you get generated names: 'firstName' and 'surname'
--- 2 inputs from which you get input Alphabets: first, last

Rust translate

• Fixed and sample tests like 001-02-2016 00:00 and 21-12-2013 02:224 should be added across all languages

• Random tests should generate cases of 3 or more trailing and leading digits above

• Reference solution should be updated (if required) to accomodate tests above

python new test framework is required. updated in this fork

CoffeeScript translation

There is a lack of tests for strict types. For example:

areEqual({ 0: 1 }, [1])

The following part of the description is misleading If the first character of either of the names given to the function is not a letter from A - Z, you should return "Your name must start with a letter from A - Z."

It implies that I should return the error message if either name does not start with a capital letter. However, the tests expect us to make our solution case insensitive. I'd suggest to rewrite it as follows:

"Your name must start with a letter from a - z A - Z."
or
"Your name must start with a letter"

Should have "Code Golf" in the title and tag.

JS: Node v12 should be used along with the appropriate assertion tools (Mocha + Chai)

Surely the counterpart for FIRST_NAME is LAST_NAME

Python translation

I accidentally added my password to the global object... Luckily I encrypted the password...

From these statements I assumed that the password is already encrypted, and we're supposed to decrypt it, but the actual requirement is to call encrypt ourselves using the password string as input.

Specify how strict the format should be. The description:

"...return true if the input is in the following date time format 01-09-2016 01:20..."

is not clear enough whether it refers to an actual valid date format or not.

For instance, it's not clear whether "99-99-9999 99:99" and "00-00-0000 00:00" are considered valid.

At least, you can mention something like:

"It doesn't reflect an actual date, it's just a date format. Which means, "99-99-9999 99:99" and "00-00-0000 00:00" are valid"

The strings are to be split on the capital letters : tests cases don't respect that. Eg: UGo7QGXIA7sSLBtPs35X expects 'UGo7 QGXIA7s SLBt Ps35 X'...