I've been migrating our tests to v3 and ran into an unusual legacy test. It creates a large number of foreground threads which do stuff and then verify success or failure by calling xunit Assert ...