HARNESS-RETRY override feature request.

Open
#273 3 comments 1 reaction 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
perl
Domain
cli, testing-qa

Research direction

Start by tracing the existing HARNESS-NO-RETRY directive and global retry handling in Yath. Add a complementary directive that enables retries only for marked tests, then verify the behavior with the relevant harness tests; done means marked tests retry without requiring HARNESS-NO-RETRY on all other files.

Written by the indexing model from the issue text.

Description

Currently, if I have thousands of test files and I only want to allow retry on a couple of them, I have to add HARNESS-NO-RETRY on all the others and start yath with a global retry.
I would like to have a harness directive that does the opposite, call it FORCE-RETRY or ALWAYS-RETRY or OVERRIDE-RETRY or something like that, so I only need to add it to a specific test that is flaky while I work on stabilizing it.
You told me after your talk it could be added to the new Yath update ;)
Thanks!

Dominant language
Perl
Stars
28
Forks
30
PR merge metrics
No merged PRs in 30d

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 Test-More/Test2-Harness

All issues in Test-More/Test2-Harness

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.