feature files in test/tests/features are being included for every cekit test
#66
Comments
jmtd
added a commit
to jmtd/behave-test-steps
that referenced
this issue
Apr 3, 2024
To prevent these feature files leaking out to all `cekit test` users, rename them with a ".disabled" suffix. They will still be cloned into every cekit test run, but will be ignored by behave. For our GHA tests, re-enable them by renaming to remove the suffix. Fixes cekit#66. Signed-off-by: Jonathan Dowland <[email protected]>
jmtd
added a commit
that referenced
this issue
Apr 3, 2024
Disable our feature files by default (#66)
jmtd
added a commit
to jmtd/behave-test-steps
that referenced
this issue
Nov 21, 2024
To prevent these feature files leaking out to all `cekit test` users, rename them with a ".disabled" suffix. They will still be cloned into every cekit test run, but will be ignored by behave. For our GHA tests, re-enable them by renaming to remove the suffix. Fixes cekit#66. Signed-off-by: Jonathan Dowland <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cekit testworks by cloning this repository totarget/test, and then copying on top the relevant behave files from the image being tested. It then invokes behave.behave operates from
target/testand includes any*.featurefile it can find: so, everycekit testrun for any image since merging #61 is picking up those feature files.They may or may not be run (depending on what tags are defined for the image), but they cause cekit tests to fail, which expect a certain number of scenarios/features/steps to be defined.
The text was updated successfully, but these errors were encountered: