Store artifacts for failed E2E test runs.

[peterwilsoncc]

In order to help review failed E2E test runs, store the screenshots and HTML artifacts of the failed runs on the GitHub actions.

This is already available on the Gutenberg repository and can be done via a simple copy and paste.

https://core.trac.wordpress.org/ticket/58596

[peterwilsoncc]

In the ​linked pull request:

• Example ​failed test run
• Example ​successful test run
• Workflow changes are a copy-paste from the ​equivalent files in the Gutenberg repo

[peterwilsoncc]

In 55991:

Build/Test Tools: Store artefacts of failing E2E test runs.

Modify the E2E workflow to store the screenshots and HTML files generated during failing tests as an artifact in the workflow.

No artefact is stored for passing test runs.

Props peterwilsoncc, isabel_brison.
Fixes #58596.

Committed r55991 / ​https://github.com/WordPress/wordpress-develop/commit/151621661b263768ff2e9b2b69b7ce5f83866c57

[SergeyBiryukov]

Thanks for the ticket!

I thought this would be helpful for investigating the timeouts in #58592, but apparently if the tests fail due to a timeout, the artifacts are not generated.

For example, a ​recent test run failed with:

Error: TimeoutError: Navigation timeout of 30000 ms exceeded

and the artifacts task says:

No files were found with the provided path: artifacts. No artifacts will be uploaded.

[peterwilsoncc]

Replying to SergeyBiryukov:

I thought this would be helpful for investigating the timeouts in #58592, but apparently if the tests fail due to a timeout, the artifacts are not generated.

Yeah, I've since learnt that. I considered reverting but decided it would be helpful to store them for other failures even if it's not useful for timeouts.