As a QA Eng, I'd like to have backstop results in test report if it failed

Open
#207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
playwright, typescript
Domain
testing-qa

Research direction

The issue mentions backstop HTML results and the shared test-results folder, but no file or test entry point. Trace where backstop runs and where failed-test artifacts are written; done means a failed test leaves a renamed HTML result in the shared report folder for later access.

Written by the indexing model from the issue text.

Description

enhancement

Currently, backstop results open while execution, and if closed it can't be reopened + not sure if we can access that in the shared report folder now.

Recommend:

  • save backstop HTML results after rename it to the failed test and keep that info in the test results folder
Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
3d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wp-media/wp-rocket-e2e

All issues in wp-media/wp-rocket-e2e

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.