Reorganize tests to be one file per module and to give more descriptive file names #193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Historically, spork's tests have been organized into numbered suites, such as
suite0002.janet
. Each suite usually contains tests related to a single module. But some suites mix together tests for unrelated modules (without an apparent intention to doing so).More recent additions and updates in the
spork/test
directory have switched to using an (IMHO) much friendlier convention. These newer test files simply name the test file after the module it is primarily focused on testing, prefixed withsuite-
. This makes test cases for a given module much easier to find. Discoverability of test cases matters because in many cases the tests are the only documentation or usage examples available for a given spork module.This PR proposes renaming and lightly reorganizing spork's tests to entirely switch over to the more recently-preferred convention. The goal is to improve the discoverability and therefore usefulness of test suites as quasi-documentation. The tests themselves are unmodified and all still pass.