tests for parameter conflict resolution #65
Draft
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
christianrauch
force-pushed
the
gtest
branch
16 times, most recently
from
7a30ad1 to
083046b
Compare
christianrauch
force-pushed
the
gtest
branch
7 times, most recently
from
9e6d763 to
671a89c
Compare
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 adds tests for the parameter handling for conflicting parameter states, such as
AeEnableandExposureTime. Tests only run when at least one real camera is detected.Note: Even if this does not run the actual unit tests on the CI, it will still run
ASan,memcheckand other tools from themixin.