cekit test works by cloning this repository to target/test, and then copying on top the relevant behave files from the image being tested. It then invokes behave.
behave operates from target/test and includes any *.feature file it can find: so, every cekit test run 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.
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.