You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is a feature request. Naturally BDD style testing will often be implemented as some kind of integration testing, maybe even black box end to end testing, as we use it. Therefore, tests might run in Mavens integration-test phase against systems started in pre-integration and teared-down in post-integration, e.g. docker containers. It is imperative, that the maven process reaches the post-integration phase at all cost to tear-down properly as also outlined in https://maven.apache.org/surefire/maven-failsafe-plugin/index.html.
Even when using the validate check upfront, it would be lovely, to somehow split the gauge-maven-plugin test execution into a test and a verify phase as the failsafe plugin does it. So even runtime errors (lot's of stuff can go wrong, e.g. classpath problems) would still allow a proper post-integration teardown.
The text was updated successfully, but these errors were encountered:
MariusSchmidt
changed the title
Split test-execution phase and verify phase
Feature request: Do not fail the Maven build for a failed test
Apr 21, 2020
MariusSchmidt
changed the title
Feature request: Do not fail the Maven build for a failed test
Feature request: Split test-execution phase and verify phase
Apr 21, 2020
Hi again,
this is a feature request. Naturally BDD style testing will often be implemented as some kind of integration testing, maybe even black box end to end testing, as we use it. Therefore, tests might run in Mavens integration-test phase against systems started in pre-integration and teared-down in post-integration, e.g. docker containers. It is imperative, that the maven process reaches the post-integration phase at all cost to tear-down properly as also outlined in https://maven.apache.org/surefire/maven-failsafe-plugin/index.html.
Even when using the validate check upfront, it would be lovely, to somehow split the gauge-maven-plugin test execution into a test and a verify phase as the failsafe plugin does it. So even runtime errors (lot's of stuff can go wrong, e.g. classpath problems) would still allow a proper post-integration teardown.
The text was updated successfully, but these errors were encountered: