[vividus] countScenarios task calculation fixing #3157
Draft
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.
countScenarios
is using properties' files (overriding.properties) instead of argumentdir
in CMD.doesn't help.
JUnit4StoryRunner runner = new JUnit4StoryRunner(StoriesRunner.class);
andrunner.getDescription()
for calculating, but there is a problem with Lifecycle Examples (Scenarios
count more than expected, butScenarios with Examples
is right). For example:Also when we specify empty directory we want to see
0 | Stories
, but now it is1 | Stories
.For executing
./gradlew countScenarios -p vividus-tests
it is necessary to specify properties inoverriding.properties
file to avoid errors (for example,Exception in thread "main" org.vividus.resource.ResourceLoadException: No ExamplesTable resource is found for /data/tables/system/mobile_app/locators/${target-platform}.table
). Also there is a problem with such scenario:After executing
./gradlew countScenarios -p vividus-tests