SFD-115: Add reports for automated tests #93
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SFD-115 Jira ticket
Adds artifact uploads in the playwright workflow for the traces and an HTML report file of the test results.
Notes:
WRT the unit tests, whilst Web Test Runner does support reporting, it seems that the experimental Angular builder which is the bridge between Angular and Web Test Runner doesn’t yet support this feature and there isn’t any documentation it so we may have to wait a bit to add reports for the unit tests.
On the Playwright front, I’ve added artifact uploads for the Playwright traces for failing tests and an HTML report using the pytest-html package which can be downloaded. @qgogay-scottlogic and @sdun-scottlogic are going to have a discussion about what sort of things we’d like to do with the test reporting (e.g. do we want to try to add a display to the GitHub UI?) and we can then investigate further in a follow up ticket.