Repository navigation
Conversation
This commit transitions the remaining boost tests into catch2, so we finally use only one testing framework instead of two. We also gain some speedups in test execution, mainly thanks to combining test source files into two main executables, speaking of... I split the framework tests into two executables to preserve the current behaviour, which is being able to exclude CCDB-labelled tests on the level of ctest (from alidist): - `o2-qc-test-core` - `o2-qc-test-ccdb` This being said, I saw that not all tests which require CCDD were labelled as such - should we fix that? For now, I added catch2 tags to such test cases, but they will not be excluded when running: ``` ctest --output-on-failure -LE (CCDB)|(manual) ``` ...which, again, preserves the current behaviour. Assisted by Claude Sonnet/Opus 5.5
Collaborator
Author
|
@Barthelemy as discussed over coffee, I can merge the two executables and then we should be able to consistently enable/disable all tests relying on CCDB, also those which historically were not labelled as such. |
This branch has not been deployed
This file contains hidden or 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
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.
This commit transitions the remaining boost tests into catch2, so we finally use only one testing framework instead of two. We also gain some speedups in test execution, mainly thanks to combining test source files into two main executables, speaking of...
I split the framework tests into two executables to preserve the current behaviour, which is being able to exclude CCDB-labelled tests on the level of ctest (from alidist):
o2-qc-test-coreo2-qc-test-ccdbThis being said, I saw that not all tests which require CCDD were labelled as such - should we fix that? For now, I added catch2 tags to such test cases, but they will not be excluded when running:
...which, again, preserves the current behaviour.
Assisted by Claude Sonnet/Opus 5.5