Orange-OpenSource / Orange-OpenSource/hurl
Provide a `repeat` variable to allow running non-colliding hurl files
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 19.2k
- Forks
- 745
- Avg merge
- 5h 3m
- Merged PRs (30d)
- 60
Description
Sometimes an hurl file has some setup calls that may fail if run more than once with the same arguments.
having the repeat variable telling which is the iteration number would make fairly easy to make --repeat work even in that case.
Contributor guide
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.
Research direction
Start by tracing how the --repeat option runs Hurl files and how variables are exposed during request execution. Define the iteration number available to each repeat, then add coverage showing that setup calls can use it to avoid collisions and that repeated runs still behave correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100