Documentation is not entirely clear on Parallelizable-Attribute
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
Hi this page https://github.com/nunit/docs/wiki/Parallelizable-Attribute doesn't look clear on the meaning of the values. I believe some clarity is required or may be examples for it just because I found this question https://stackoverflow.com/questions/50995496/nunit-difference-between-parallelscope-selfchildren-fixturechildren-and-all and some one also has issue with understanding it.
I did some time ago few tests and it looked like ParallelScope.Children is what I need, I needed to run one suite at a time and all the tests of that suite should be run in parallel, once tests of that suite are executed the next suite is taken for execution. As an exception I may need to run a suite with other suites and I was thinking that I can run that suite with ParallelScope.All. Right now it looks like I had a wrong understanding how ParallelScope.Children works as it seems that at some moments I see tests executed at the same time from 2 different suites which are marked
with ParallelScope.Children.
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 with the Parallelizable-Attribute wiki page and the linked Stack Overflow question to identify which ParallelScope values are confusing. Verify the reported behavior of Children and All, then update the page with clearer definitions or examples. Done means the values and suite-execution behavior are understandable without relying on external discussion.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100