VED-1036 Tidy up pipeline reports

[dlzhry2nhs]

Summary

• Routine Change

Existing problem:
All pipelines generate and publish an allure report. This is not strictly needed, and given the use of Github Pages, we can run into a potential race condition.

Proposed solution:
As suggested by Fatima, on the regular dev PR and CI/CD pipelines, we only really need the test output from the console, and additionally could display the nicer XML BDD summary.
However, we should limit the allure report to only fire on manual dispatch. Usually there would only be one running at a time and this is mainly used by automation testers.

Changes:

• separated out the jobs that run the tests and the one that creates the report
• made the test report job depend on the tests run being completed - failed or succeeded
• ensure that on pipeline CI/CD, PR we only publish the simple xml output, and when run manually we also include the Allure report

Testing:

Tested in the PR pipeline of this ticket:

• https://github.com/NHSDigital/immunisation-fhir-api/actions/runs/21515617445

Demonstrated that only the xml output is provided and Allure reports are skipped. You can navigate to the workflow summary to see the BDD report, although for most devs the standard Github runner output logging should suffice.

Tested using the manual pipeline twice with 2 different sets of tests:

• https://github.com/NHSDigital/immunisation-fhir-api/actions/runs/21515170108
• https://github.com/NHSDigital/immunisation-fhir-api/actions/runs/21515258599

Demonstrated that Allure reports were published. The latest report is always published to the Github Pages:

Reviews Required

• Dev
• Test

Review Checklist

ℹ️ This section is to be filled in by the reviewer.

• I have reviewed the changes in this PR and they fill all of the acceptance criteria of the ticket.
• If there were infrastructure, operational, or build changes, I have made sure there is sufficient evidence that the changes will work.
• If there were changes that are outside of the regular release processes e.g. account infrastructure to setup, manual setup for external API integrations, secrets to set, then I have checked that the developer has flagged this to the Tech Lead as release steps.
• I have checked that no Personal Identifiable Data (PID) is logged as part of the changes.

[github-actions]

This branch is working on a ticket in the NHS England VED JIRA Project. Here's a handy link to the ticket:

VED-1036

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud