You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 12, 2017. It is now read-only.
Currently, the in-editor test discovery uses the xunit1 API, rather than the xunit2 API that allows for custom test discovery. To use the xunit2 API to discover tests:
Host an AppDomain that will be used for test discovery
The custom AppDomain to (shadow) load the xunit2 API from the output directory. What happens if the project has been cleaned?
Monitor the output directory for changes to any of the referenced assemblies (any of them might contain custom test discoverers), and tear down and reinitialise the AppDomain. This will have nasty implications for performance - reinitialising the AppDomain on each build. Can we get notified of the assemblies used for discovery, so we can only reset if the appropriate assemblies have changed?
Once the tests are discovered by xunit2, serialise them to the external test runner, so we don't have to discover them again