Having 140 000 tests is not the correct way to test for performance and makes successful testing of a compliant solution take ten seconds. Correctly testing for performance can be done in less than a second for compliant solutions while consistently timing out for uncompliant ones. Testing can be valid and responsive.

Please also refer to the documentation.

• missing a performance tag.
• the typical size of the inputs and the number of tests should to described
• an example about the quotes should be in the description too (if the behavior is kept)

adasfA# A$#A@! A$$@!DAA A#!@FA-A#@!F-A@#¨G-AA@!FFA
expected false to deeply equal true

What is a word?

Duplicate of all the string-translating katas.