There is no point in this kata. Literally everything is hot garbage. ;-)

better description and more test cases are required

The description has many typos, and does not provide adequate explanation. Anyone who knows what JSON is will likely find this kata far too simple; given the difficulty level, it would be appropriate to explain JSON in the description, or at the very least, provide a link to an explanation. The single example is not enough.

Seems like the point of the challenge was to implement JSON.stringify(), no?

Not set up to have variable accesssed by function

The word 'easier' is misspelled.

Instructions are unclear.

Typos and capitalization errors in the description. Also Kata only really makes sense when you look at the test cases, so description should be more detailed.

The description should elaborate on what is required. Without test cases this would have been much more confusing.

I think it's meant to be, providing "Object" is already 70% of the solution. I think just providing //your code here would be less confusing.

Solution is basically in test cases. Also not so informative use case in description.

The description suggests that one should create a JSON compatible object, but the tests only compare strings.

The initial solution doesn't reflect that you want to use a.toJson, e.g. change the Object prototype.