single spec for all literal tests

[kbrock]

This code confuses me, as 99% of the time, there is a single spec per lib file.
Textmate and sublime uses this assumption to switch between tests too.

Do these really need to be separate files?

Is the problem here that the test app is too simple?

[mbj]

Do these really need to be separate files?

No, the fact these are separate files is from a very ancient mutant version that did use the file name as matching criteria.

Is the problem here that the test app is too simple?

The test app is a minimal integration test. It should have the following sematics under mutation testing:

• A fully covered subject
• A partially covered subject
• Does not maintain mutable global state
• Has instance methods
• Has singleton methods
• (future) has subjects with failing tests

What kind of mutations are happending is not important (anymore), since the full mutation specification is in the mutant-meta so mutation wise it should NOT be exhaustive.

[mbj]

@kbrock After I pushed c392cb5 this does not merge clearly anymore. The rebase on your side should be trivial as I only nuked redundant encoding headers.