Table of contents


End to end testing publishing apps

We have end to end tests running against proposed changes to applications to verify that the change doesn’t break flows interacting with multiple applications.

Flaky tests

These tests execute through the UI, and can be fragile and flaky as a result. Rerunning a build may fix the immediate problem but you are implored to tackle the root cause.

Test against branch

The test-against branch is used by Jenkins when executing the test suite against proposed changes. This branch should get pushed to automatically whenever a change is made to master branch. On occasion the master branch has failed due to the flaky nature of the test suite causing test-against to become behind master. Rerunning the master branch build should fix it.

If you are making changes to publishing-e2e-tests itself, push your branch up to GitHub and then trigger a build of your branch from the branch list.

How to add new tests

If you are writing a new publishing application or wanting to cover new end to end flows you are advised to read the guidance on Github.

This page was last reviewed on 1 March 2019. It needs to be reviewed again on 1 September 2019 by the page owner #govuk-developers .
This page was set to be reviewed before 1 September 2019 by the page owner #govuk-developers. This might mean the content is out of date.