diff options
Diffstat (limited to 'ci-arch.html')
| -rw-r--r-- | ci-arch.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/ci-arch.html b/ci-arch.html index 52b30ab..c9ee5a6 100644 --- a/ci-arch.html +++ b/ci-arch.html @@ -49,7 +49,7 @@ <li><a href="#capacity-tests-non-functional-requirements">Capacity tests, non-functional requirements</a></li> </ul></li> <li><a href="#ci-implementation">CI implementation</a></li> -<li><a href="#automated-acceptance-tests-for-ci">Automated acceptance tests for CI</a></li> +<li><a href="#automated-acceptance-tests">Automated acceptance tests</a></li> </ul> </nav> <h1 id="introduction">Introduction</h1> @@ -284,7 +284,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="ci-implementation">CI implementation</h1> <p>FIXME This needs to be written, but it needs a lot of thinking first</p> -<h1 id="automated-acceptance-tests-for-ci">Automated acceptance tests for CI</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> |