Convert xUnit tests to MSTest and increase use of traversal projects to increase build perf #605
Conversation
barnson
force-pushed
the
bob/MSTestTraversal
branch
3 times, most recently
from
0603501 to
8b1989b
Compare
|
Is the migration from xUnit to MSTest due to extra functionality in MSTest, or an issue with xUnit? xUnit does have support for the Microsoft Testing Platform If it's just about parallel testing, it seems this could just be a case of missing parallel enabling in xUnit? I'm keen on having a try of this and potentially seeing how it goes with the code coverage extension. |
|
Getting .exe test assemblies was a necessary part of a multiproc build. Now that xUnit supports it, I wouldn't be opposed to using it but I found MSTest to offer a better developer experience (e.g., with an MSBuild SDK). |
|
@robmen The action runner VM got caught up in the long-running tests (Sql and Firewall). That's a downside of the segment scope though in this case, there's not much after |
- Move ext\ unit tests to MSTest. - MSBuildify ext projects with MSTest execution. - Fork test support projects for MSTest: - WixInternal.TestSupport - WixInternal.Core.TestPackage
***Does not include a full conversion to traversal projects. The wix segment already uses traversal projects extensively so there isn't a significant per win, especially compared to the effort required...but MSTest's method-level parallelism cuts test run time in half (~60->~30).
barnson
force-pushed
the
bob/MSTestTraversal
branch
from
8b1989b to
6ca404f
Compare
Work for wixtoolset/issues#8685.