Method for disabling plugins
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 827
- Forks
- 138
- PR merge metrics
- No merged PRs in 30d
Description
Some method callable from within a plugin to turn itself off or disable certain classes of its own hooks. (e.g. If there is some setup running at the beginning of each test case and teardown at the end of each testcase. If setup fails then teardown, should not be attempted.) Would like to implement this in a generalized way.
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
The issue does not name files, tests, or an entry point. Start by tracing how nose2 invokes plugin hooks around each test case, especially setup and teardown, and determine how a plugin could disable itself or selected hook classes after setup fails. Done means a generalized, documented behavior with tests covering skipped teardown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100