Make WordPress Core

Opened 10 months ago

Closed 10 months ago

Last modified 10 months ago

#58596 closed enhancement (fixed)

Store artifacts for failed E2E test runs.

Reported by: peterwilsoncc's profile peterwilsoncc Owned by: peterwilsoncc's profile peterwilsoncc
Milestone: 6.3 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: has-patch
Focuses: Cc:

Description

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.

Change History (6)

#3 @peterwilsoncc
10 months ago

  • Resolution set to fixed
  • Status changed from assigned to closed

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.

#5 follow-up: @SergeyBiryukov
10 months ago

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.

#6 in reply to: ↑ 5 @peterwilsoncc
10 months ago

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.

Note: See TracTickets for help on using tickets.