Fix issue where a non-boolean variable passed into a testclass would skip the test#220
Merged
jcollins1983 merged 1 commit intoPyFixate:mainfrom Mar 1, 2026
Merged
Conversation
jcollins1983
approved these changes
Mar 1, 2026
Collaborator
jcollins1983
left a comment
jcollins1983
left a comment
There was a problem hiding this comment.
Looks like a sensible change.
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
2 participants
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.
In a test script we were accidentally passing a variable that was not consumed by the function and therefore was passed to the parent class (the testclass) this would then be interpreted as the "skip" variable. The check in sequencer.py does not check if the value is a boolean.
This could result in a code mistake in a test script "silently" skipping a test without being noticed. Unless you go look at the logs.
The issue test script:
Sequencer.py
