summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTails developers <amnesia@boum.org>2014-05-12 16:47:50 +0200
committerTails developers <amnesia@boum.org>2014-05-12 16:47:50 +0200
commit9038a7829be3c6b8289cae2a5a3c54747fc567ec (patch)
tree2eea12f9d05aa9ce67e27692d6dbf23c10e16f04
parentd1d73417532d62f1ccdad54aa6bf643d96c02736 (diff)
Revert "Add tag mechanism for skipping tests."
This reverts commit 2394106cca556a1326c4624be4768cb6835a6d22. This may easily lead us to forget about these tests, so we'll have to invent a more involved mechanism for tests expected to fail.
-rwxr-xr-xrun_test_suite5
-rw-r--r--wiki/src/contribute/release_process/test/automated_tests.mdwn5
2 files changed, 2 insertions, 8 deletions
diff --git a/run_test_suite b/run_test_suite
index 390d567..f90efd1 100755
--- a/run_test_suite
+++ b/run_test_suite
@@ -184,9 +184,8 @@ export JAVA_HOME="/usr/lib/jvm/java-6-openjdk-amd64"
export SIKULI_HOME="/usr/share/java"
export DISPLAY=${TARGET_DISPLAY}
check_dependency cucumber
-CUCUMBER_OPTS="--tags ~@skip --format ExtraHooks::Pretty"
if [ -z "${*}" ]; then
- cucumber ${CUCUMBER_OPTS} features
+ cucumber --format ExtraHooks::Pretty features
else
- cucumber ${CUCUMBER_OPTS} features/step_definitions features/support ${*}
+ cucumber --format ExtraHooks::Pretty features/step_definitions features/support ${*}
fi
diff --git a/wiki/src/contribute/release_process/test/automated_tests.mdwn b/wiki/src/contribute/release_process/test/automated_tests.mdwn
index ffb5fef..3ee785c 100644
--- a/wiki/src/contribute/release_process/test/automated_tests.mdwn
+++ b/wiki/src/contribute/release_process/test/automated_tests.mdwn
@@ -297,11 +297,6 @@ of this, see the `I set sudo password ...` step in
into a class variable so it can be used by, among others, the `I enter
the sudo password ...` step.
-## Skipping broken tests
-
-Any features or scenarios that will be broken for an extended time can
-be *completely* skipped by tagging them `@skip`.
-
# Limitations and issues
These things are good to know when developing new features, scenarios