Hi!
So I've been trying to run a single test using the acceptance-test-harness,
without success:
JENKINS_WAR=../jenkins/war/target/jenkins.war mvn
-Dcucumber.test=features/freestyle_build.feature:10 test
=> leads to all features trying to be executed,
instead of just the single one passed above..
I noticed this arg in the pom file, which likely explains that behavior:
<argument>${project.basedir}/features</argument>
=> runs all features.
Note: no arg means that the cucumber Main class will simply run all
features.
So it seems (to me) like the pom's cucumber.test-activated profile does
*not* succeed at passing its single test to the above execution.
Anybody concurs or knows how to work-around that behaviour?
(Could simply be a known limitation as the framework matures.)
Thx,
Marco.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
