Make backstopjs test more compatible with test cucumber test run report
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- testing-qa
Research direction
No files or tests are named. Start by tracing the BackstopJS visual-regression steps in the step definitions and how the test session produces the CLI and Cucumber report. Done means BackstopJS failures appear directly in the CLI and can be included in the Cucumber report, without skipping those steps.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
We need to make backstopjs test more compatible with the test session, so that when it fails, we also get it directly in the CLI for the test that it is failed with the possibility of having this in the cucumber report.
Right now, we backstopjs vr steps those tests in the step definition, so I when we implement this, we shouldn't skip those anymore.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wp-media/wp-rocket-e2e
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wp-media/wp-rocket-e2e#407 ·
-
Fatal guard e2e plan Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wp-media/wp-rocket-e2e#396 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wp-media/wp-rocket-e2e#408 · 1 comment ·
-
Flaky test round 3 Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
wp-media/wp-rocket-e2e#406 · 4 comments ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 68/100
wp-media/wp-rocket-e2e#399 · 3 comments ·
All issues in wp-media/wp-rocket-e2e
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·