microsoft / microsoft/testfx

MTP Extension - Flaky Tests

Open
#4,931 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/mtp area/mtp-extensions type/discussion
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.