Push retries count to test report to be extracted in Metabase

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
playwright, typescript
Domain
analytics, testing

Research direction

Locate the Playwright test-report generation entry point and inspect how retry information is currently represented. Confirm the report exposes a per-test retry count that Metabase can extract, then validate it with a test that retries.

Written by the indexing model from the issue text.

Description

Currently, we have some tests that go through retries, will be nice to know which tests are going through retries the most and try to refactor that so it won't need retries

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.