feat: filter test execution by test plan case IDs #155
Conversation
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
Enhanced functionality to execute only the test methods specified in a test plan. ### Details: - **Filter logic**: Test methods are filtered based on matching case IDs from the test plan. - **Fallback behavior**: If no case IDs are defined, all test methods are executed as usual. - **Configuration**: Case IDs are sourced via the `QASE_TESTOPS_PLAN_ID` environment variable or `qase.config.json`.
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 pull request includes a version update for the
qase-javaproject to 4.0.4 and introduces new functionality for the Junit5 reporter. The most important changes include the addition of support for running tests included in a test plan for Junit5, updates to thepom.xmlfiles to reflect the new version, and an upgrade of thejunit-platform-enginedependency.New functionality:
qase.config.jsonfile or through theQASE_TESTOPS_PLAN_IDenvironment variable. (changelog.md: [1]qase-junit5-reporter/src/main/java/io/qase/junit5/Junit5PostDiscoveryFilter.java: [2]qase-junit5-reporter/src/main/resources/META-INF/services/org.junit.platform.launcher.PostDiscoveryFilter: [3]Version updates:
pom.xmlfile and all module-specificpom.xmlfiles. (pom.xml: [1]qase-api-client/pom.xml: [2]qase-api-v2-client/pom.xml: [3]qase-cucumber-v3-reporter/pom.xml: [4]qase-cucumber-v4-reporter/pom.xml: [5]qase-cucumber-v5-reporter/pom.xml: [6]qase-cucumber-v6-reporter/pom.xml: [7]qase-cucumber-v7-reporter/pom.xml: [8]qase-java-commons/pom.xml: [9]qase-junit4-reporter/pom.xml: [10]qase-junit5-reporter/pom.xml: [11]qase-testng-reporter/pom.xml: [12]Dependency update:
junit-platform-enginedependency from version 1.6.2 to 1.9.0. (pom.xml: pom.xmlL38-R38)