This repository has been archived by the owner on May 3, 2024. It is now read-only.
refactor test setup and build #22
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
- allow users to specify config files to run through fire during ctest. These configs are run within the module's testing directory in the build directory (build/<module>/test) and are just checked to not have failed - the Catch test is run for each module that appends any sources to it and only tests with that module's name as a tag are run. For each module, the catch test is also run from within is build/<module>/test directory and all the files from the source test directory are symlinked into this directory for reading purposes if needed.
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
allow users to specify config files to run through fire during ctest.
These configs are run within the module's testing directory in the
build directory
(build/<module>/test) and are just checked to not havefailed
the Catch test is run for each module that appends any sources to it
and only tests with that module's name as a tag are run. For each
module, the catch test is also run from within is
build/<module>/testdirectory and all the files from the source test directory are
symlinked into this directory for reading purposes if needed.