i think that's bad:

Expected: <System.Exception>
But was: <System.InvalidCastException: Invalid cast from 'DateTime' to 'Double'.

why should i catch a specific exception just for throw an new System.Exception?

The error message is bad, but it says the position for one of the entry is wrong (should be at 2nd position, but your code places it at 3rd)

Also, your code seems to only modify the value for each key-value pair of Dictionary, but not sort it accordingly.

Everything in C# is associated with classes and objects, the same could not be said for JS (So, the OOP construct in initial solution setup and tests should be removed)

No random tests in C#

• Description should be language-agnostic (Not sure how to do that with the current inconsistent requirements)

• As a follow-up from issue by bouchert below, the sorting criteria for tie cases need to be mentioned clearly, as in whether the order breaker should be based on alphabetical order of names / their original position in the input / etc...

• In C# we are given a Dictionary, whereas in JS we are given an array of Objects.

• Also for output, C# expects a Dictionary whereas JS expects an array of Objects again...

Not only were there no random tests. it was basically just one test, testing a minimal amount of the result.

JavaScript fork

Adding some well needed random tests, and updating to chai

This seems to be fixed now

Can you approve my decision?

i can't approve my translation

Too late.

JavaScript tests work fine now.

This kata doesn't make sense in a language that has arbitrary precision integers.