Scenario for RequiresThread Attribute on Assembly level?
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
Hi all,
Referring to: https://github.com/nunit/docs/wiki/RequiresThread-Attribute
does anyone know a scenario for putting the RequiresThread attribute on Assembly level?
Reason for this question is that we observed that anyway - even without the attribute - a separate thread is started for each assembly. This seems to be true for at least console runner and running tests with Resharper.
It would be very helpful for me to know in what cases it is useful to have this attribute on assembly level. Any help will be highly appreciated. Thanks in advance!
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 RequiresThread Attribute wiki page linked in the issue and compare its assembly-level guidance with the reported behavior in the console runner and ReSharper. Determine whether a documented assembly-level scenario exists, then update the documentation with a clear explanation or resolve the question if the attribute has no useful assembly-level case.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100