[Breaking] Move UWP/WinUI support to separate packages
Open
Nobody has claimed this yet.
area/mstest
type/breaking-change
- Dominant language
- C#
- Stars
- 1k
- Forks
- 312
- Avg merge
- 7h 46m
- Merged PRs (30d)
- 465
Description
Today we pack everything in MSTest.TestFramework. It's a better idea to split UWP/WinUI support into new NuGet packages, MSTest.UWP and MSTest.WinUI. This will also make the packaging fitting into lib more naturally instead of us trying to detect the platform and plugging the assemblies ourselves.
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 by locating how MSTest.TestFramework currently packages UWP and WinUI support and how platform detection plugs assemblies into lib. Define the boundaries for the proposed MSTest.UWP and MSTest.WinUI packages, then verify that the resulting packaging no longer needs the existing platform-specific assembly handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100