Three years later...

I have updated Ruby, JS, and CoffeScript to use assertEquals now that they can be edited again.

:(

Yes, I agree with you. Unfortunately, the Kata is no longer editable.

lol

I find the usage of Test.expect(actual == expected, "should be expected"); less optimal in comparison with Test.assertEquals(actual, expected); regarding test assertion output.

This would be especially helpful in "Submit tests", where we can't see your input.

The only information those failing tests give me is that it "should be something" but not what it actually was. :(

Ah, oops! OK, I've amended that test case so it should work both ways. Thank you!

The current solutions were invalidated anyway on the "should render the leaderboard with a subset of users" test - the leaderboard variable still contains all 100 names.

Great point, that's a much better way to do it! I've updated the example test cases and test cases to use your suggested tests. I've also kept the leaderboard array preloaded so current solutions won't be invalidated, but hopefully people will use your way going forward. Thank you! =)

Thank you for the feedback! I've updated the comments so hopefully they're a little more clear now.

Oops! Maybe I was thinking that I want you to also desire making the anchor tag. More likely I should just proofread better =). Thanks!

I absolutely agree. The "react" way is to pass data in from the top and not use a global array...

Thanks for reporting this! Should be all taken care of now =)

Ah, sorry about that! Last time I let myself publish a Kata late at night =). Should be fixed now.

The Creating Elements with React link currently goes to the kata's Edit page.

Typo: "I would want you to want you to" s/b: "I would want you to"