|author||intrigeri <email@example.com>||2015-07-09 14:43:26 +0000|
|committer||intrigeri <firstname.lastname@example.org>||2015-07-09 14:43:26 +0000|
1 files changed, 2 insertions, 2 deletions
diff --git a/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn b/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn
index 273224d..4143835 100644
@@ -77,7 +77,7 @@ This section heavily depends on the discussion about the previous one.
The automated test suite MUST have access to the artifacts of a given
automated build corresponding to a given commit, as well as to the
-ISOs of the previous Tails release.
+ISO of the previous Tails release.
The automated test suite MUST be run in a clean environment, using a
fresh _--tmpdir_ for each run.
@@ -89,7 +89,7 @@ When [[!tails_ticket 9515]] and friends will be resolved and a first
deployment of the automated test suite will clarify its need, we'll see
if it should be able to accept a treshold of failures for some features
before sending notifications. This could help if a scenario fails
-because of a network congestion
+e.g. because of a network congestion.