Fix problem with tests declared with nonalphanumeric characters in their name

[derekcroft]

If I define my unit tests declaratively and use characters that are not alphanumeric, the Declarative module tries to generate a test method with an invalid name. For example:

test "method's return value" do

something

end

Generates a test method called "s_return_value". This sucks when the tests run (especially in an IDE) because the test name displayed doesn't make any sense. It also leads to some tricky bugs. If I have another test method in the same suite like this:

test "other method's return value" do

something

end

The Declarative module has now blown away the first test method without telling me. Gross.

This change MIME-encodes any nonprintable characters in the test method name, avoiding this issue.

[pixeltrix]

Firstly I'm pretty sure that Declarative would raise on a duplicate test name and secondly why not use parameterize and underscore?

>> "method's return value".parameterize.underscore
=> "method_s_return_value"

Also you would need to write some tests.