calabash-android run ../android/app/build/outputs/apk/app-debug.apk -p android features/login.feature --tags ~@dont_run
-->
0 scenarios
3 steps (3 passed)
----------------------------------------------------------------------
calabash-android run ../android/app/build/outputs/apk/app-debug.apk -p android features/login.feature --tags ~@dont_run_feature
-->
0 scenarios
0 steps
----------------------------------------------------------------------
Where all scenarios in the file are tagged with @dont_run and the file itself is tagged with @dont_run_feature.
We have seen this in both calabash-android and calabash-ios.
Is our expectation wrong, or is calabash misbehaving?
Thanks,
--Carl
Feature: Should the Background run if no Scenario runs?
Background: Given no scenario runs, should the background?
@manual Scenario: Scenario1 Given This scenario should not run
@manual Scenario: Scenario2 Given This scenario should not run
mvn test -Dcucumber.options="classpath:skeleton/my_first.feature --tags ~@manual"
0 Scenarios
0 Steps
0m0.000s
Tests run: 0, ...
cucumber src/test/resources/skeleton/my_first.feature --tags ~@manual
0 scenarios
1 step (1 undefined)
0m0.006s
You can implement step definitions for undefined steps with these snippets:
Given(/^no scenario runs, should the background\?$/) do
pending # ...
end