Skip to content

[A2-6739] updating deploy yaml with option to run e2e tests #3355

Open
marcpodgorney81 wants to merge 3 commits intomainfrom
POC-run-e2e-tests-with-deploy
Open

[A2-6739] updating deploy yaml with option to run e2e tests #3355
marcpodgorney81 wants to merge 3 commits intomainfrom
POC-run-e2e-tests-with-deploy

Conversation

@marcpodgorney81
Copy link
Copy Markdown
Collaborator

@marcpodgorney81 marcpodgorney81 commented Mar 3, 2026

Describe your changes

In order to further enhance our pipeline process it would be good to run some of the e2e tests following deploy of backoffice into an environment

This would provide following benefits

  • quick feedback on if any issues with deploy process (e.g. azure)
  • quick feedback on if app and key user journeys are working
  • opportunity to run a regression set of tests, reducing amount of manual testing required
  • give confidence in version of backoffice being deployed, especially if release branch
  • give confidence in version of backoffice that are planning to release in production

As such we have updated the deploy yaml to add extra step that will run the e2e tests (in a similar way to for PRs). It has been configured as a parameter which is defaulted to enabled, see screenshot

Screenshot 2026-04-13 at 14 59 21

As with the PR e2e tests, there are settings which can be updated to determine which tests run and where, which have been setup in a new library here https://dev.azure.com/planninginspectorate/appeals-back-office/_library?itemType=VariableGroups&view=VariableGroupView&variableGroupId=149&path=cd_e2e-deploy

As with the PR tests it is currently setup to run those tagged as part of smoke set, however this also presents an opportunity to identify and tag a more in depth (i.e. regression) set of tests that could run

variables for the test run (e.g. base urls) are stored in libraries named for the environment, e.g. here for dev https://dev.azure.com/planninginspectorate/appeals-back-office/_library?itemType=VariableGroups&view=VariableGroupView&variableGroupId=50&path=cd_dev

These are passed in via an extension of the base template https://github.com/Planning-Inspectorate/common-pipeline-templates/blob/24d56ce8475c63eb471af7974073446e63480f42/stages/wrapper_cd.yml#L202

Issue ticket number and link

https://pins-ds.atlassian.net/browse/A2-6739

@marcpodgorney81 marcpodgorney81 requested a review from a team as a code owner March 3, 2026 15:47
@gmmagruder gmmagruder force-pushed the POC-run-e2e-tests-with-deploy branch from 2f65173 to 82423b0 Compare March 26, 2026 16:47
Snasim21
Snasim21 previously approved these changes Mar 26, 2026
Snasim21
Snasim21 previously approved these changes Mar 30, 2026
Marc Podgorney and others added 3 commits March 31, 2026 10:06
…cket)

fix(infrastructure): run e2e script task in deploy config (no-ticket)

fix(infrastructure): add parameter to run e2e tests job (no-ticket)

fix(infrastructure): remove display name (no-ticket)

fix(infrastructure): remove display name on step (no-ticket)

fix(infrastructure): move script into job (no-ticket)

fix(infrastructure): check if script caused issues (no-ticket)

fix(infrastructure): use e2e dev variable group only (no-ticket)

feat(infrastructure): add script check for running e2e tests in deploy (no-ticket)

fix(infrastructure): environment check in deploy (no-ticket)

feat(infrastructure): add e2e step to deploy (no-ticket)

feat(infrastructure): add checkout step (no-ticket)

feat(infrastructure): update e2e step (no-ticket)

feat(infrastructure): add app env var to e2e step (no-ticket)
@gmmagruder gmmagruder force-pushed the POC-run-e2e-tests-with-deploy branch from 84e9f44 to 1ae4426 Compare March 31, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants