stride3d / stride3d/stride

xUnit transition Epic

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Build bug Epic
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Recently switched from NUnit to xUnit, but the transition is not finished yet.

Things to still do:

  • Windows embedded self-contained runner .exe (rather than having hundreds of Main )
  • iOS, Android and UWP runners (will also need ability to report results to Teamcity and work with gold images cf #15)

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

Start by reviewing the remaining xUnit transition work described in this issue, especially the Windows embedded self-contained runner and the iOS, Android, and UWP runners. Identify how runner results should reach TeamCity and how gold-image support relates to #15. Done means the listed platform runners and reporting requirements are implemented and the transition no longer depends on hundreds of Main methods.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev, testing-qa
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.