Testing framework #53
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@SaoirseWard there are a few typos in the "The Testing Environment" page. Could you have a look and squash these? |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The test and input directories have been restructured in order for it to be easier to create quick-to-run tests. The test subdirectories and what they contain was based on the original test/SConscript file and how it broke up the testing components. build.sh has been edited to count .unit in the test child directories as opposed to the test directory. The test/SConscript file has been edited to call each SConscript file in the child directories. Each test subdirectory has an SConscript file to call the tests in the directory. Each input file has been checked to determine if it is working and the tests that do not work have been moved to the Obsolete subdirectory. The other .in files have been sorted based on what they test. Documentation has been written to explain each test as well as the testing infrastructure and how to create a new test.