Same! Add in some Infinity, NaN, 'More please' etc. into the tests as well to get some basic validation and a bit of fun

PascalCase not camelCase
When will people learn?

I'm amazed to see so few approaches like this... memoization was my first thought!

Case

This would be nice if the kata description were more complete
Looking over the solutions, almost none are approaching production quality. You don't need regexes or some byzantine logic. The time available is easily adequate as your select should complete in << 1 second.
Real incoming data has Mr, Dr etc. in (as this has), with all sorts of separators from commas to slashes. Some at work includes 'MRS DR PROF' and such, sometimes as a prefix, sometimes as a suffix.

The tricky, and beautiful, task here is to figure out that this is the case.

Nicely written kata. It feels like it could be built upon to make a higher tier kata with multiple rolls / battles quite easily.

If you can find some examples that would result in floating point errors, that would be a good test, many of the current solutions would fail such a test.
https://0.30000000000000004.com/

See also Pascal Case, which is where you're confused. Stop confusing new coders with this and leaving everyone else having to pick up after you.

The first letter of the first 'word' of a camel case string should NOT be capitalised.

What sort of kata is this where the very basis of it is wrong? The idea that this character should be capitalised if the numpty who wrote the original screwed it up is daft. This is as bad as some of the rubbish I'm asked to do code reviews on.

https://en.wikipedia.org/wiki/Camel_case

Should throw some nulls, undefineds, numbers as strings, 0xFF etc. values into the tests. There are a lot of solutions where the usual dodgy input that we get in production would cause them to fall over, and as is it's a bit easy for 5 kyu.

For javascript this is a trivial kata (7 or 8 kyu), is it rated as 6 because of difficulties in other languages?