MTP Extension - Flaky Tests
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 312
- Avg merge
- 8h 30m
- Merged PRs (30d)
- 469
Description
This would need a backing storage that can persist in between test runs.
This is obviously doable by creating an interface that the user consumes. But the way extensions are set up is that they're auto registered aren't they?
Have you got mechanisms for registering extensions that might require input, without rewriting your own entry method?
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
No files, tests, or entry points are named. Start by tracing how extensions are auto-registered and how test state could persist between runs, then clarify the required registration input and backing-storage interface. Done would mean an agreed, implementable design for supporting this extension scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100