summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <lwirzenius@wikimedia.org>2019-05-07 16:10:19 +0300
committerLars Wirzenius <lwirzenius@wikimedia.org>2019-05-07 16:10:19 +0300
commit9542dedc47cf036a33a6689ef6e6b2b2d071eefb (patch)
tree5d842bfdfb3d6aeb99d6b98a346d8d184d896126
parentf52ce479fbf21f8b9da5f0449d5a7007b98a9cd7 (diff)
downloadwmf-ci-arch-9542dedc47cf036a33a6689ef6e6b2b2d071eefb.tar.gz
Change: heading for acceptance tests
-rw-r--r--ci-arch.html4
-rw-r--r--ci-arch.mdwn2
-rw-r--r--ci-arch.pdfbin286470 -> 286485 bytes
3 files changed, 3 insertions, 3 deletions
diff --git a/ci-arch.html b/ci-arch.html
index a2e4d45..197cd5d 100644
--- a/ci-arch.html
+++ b/ci-arch.html
@@ -50,7 +50,7 @@
<li><a href="#capacity-tests-non-functional-requirements">Capacity tests, non-functional requirements</a></li>
</ul></li>
<li><a href="#architecture-internals">Architecture: internals</a></li>
-<li><a href="#acceptance-criteria">Acceptance criteria</a></li>
+<li><a href="#automated-acceptance-tests">Automated acceptance tests</a></li>
</ul>
</nav>
<h1 id="introduction">Introduction</h1>
@@ -285,7 +285,7 @@
<p>Capacity tests, and other tests for non-functional requirements, will also be done in dedicated, isolated production-like environments. RelEng will work with the performance team to sort out the details.</p>
<h1 id="architecture-internals">Architecture: internals</h1>
<p>FIXME This needs to be written, but it needs a lot of thinking first</p>
-<h1 id="acceptance-criteria">Acceptance criteria</h1>
+<h1 id="automated-acceptance-tests">Automated acceptance tests</h1>
<ul>
<li><p>FIXME: This chapter will sketch some automated acceptance tests using a Gherkin/Cucumber-like pseudo code language. Or in some other way that can be automatically executed.</p>
<p>The goal is to have CI deploy itself, and as part of the pipeline run acceptance tests defined here.</p></li>
diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index ee32a82..21b5dcd 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -713,7 +713,7 @@ RelEng will work with the performance team to sort out the details.
FIXME This needs to be written, but it needs a lot of thinking first
-# Acceptance criteria
+# Automated acceptance tests for CI
* FIXME: This chapter will sketch some automated acceptance tests
using a Gherkin/Cucumber-like pseudo code language. Or in some other
diff --git a/ci-arch.pdf b/ci-arch.pdf
index b9f6c81..a60b283 100644
--- a/ci-arch.pdf
+++ b/ci-arch.pdf
Binary files differ