Last modified: 2013-05-06 16:07:24 UTC
a "@beta-only" tag would be useful right now to turn off AFTv5 tests for test2 until we can get the config there to match beta.
I am actually working on a completely different solution to the problem. Tagging features/scenarios that should not be run on a browser/site never looked good to me. (Regardless of the fact that it was my idea, replacing another idea that I previously had and that I did not like.) At the moment I think the way to go is to use Cucumber command line option: -e, --exclude PATTERN Don't run feature files or require ruby files matching PATTERN For an early draft of the idea, take a look at: https://wmf.ci.cloudbees.com/job/browsertests-commons.wikimedia.beta.wmflabs.org-linux-chrome/configure
Looks like --exclude command line option only skips the entire file. I could not find a way to skip just a scenario. Looks like we will need tags for scenarios. I still think features should be skipped with --exclude command line option.
Related URL: https://gerrit.wikimedia.org/r/61574 (Gerrit Change I77b189137498c687953192e8c7a887fa1069c65e)
Related URL: https://gerrit.wikimedia.org/r/61576 (Gerrit Change If0958819d4ca0c8f3e5921e875449ef537949109)
Related URL: https://gerrit.wikimedia.org/r/61582 (Gerrit Change I930fde6cb171864687d2e948bf5013695a73e1a5)
Related URL: https://gerrit.wikimedia.org/r/61586 (Gerrit Change I40ba871edcba53c7f29665deb0fb45836b6ececf)
Related URL: https://gerrit.wikimedia.org/r/61587 (Gerrit Change I9abebfa0252c013f4be86a9bab30a252e68c7637)