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 has been archived by the owner on May 19, 2023. It is now read-only.
I have a single test project with over 77,000 tests in it. Running the tests on .NET Core using dotnet test, these tests are both discovered and complete running within 4 minutes.
However, when loading a project that uses xunit.runner.devices on MonoAndroid90 (using the Android emulator on Windows 10), it takes about 50 minutes just to discover the tests. Subsequently, the tests will run for over an hour before they crash the runner. Here is the log of the crash:
At least for the test discovery part, I noticed that in the xunit.runner.visualstudio project is not loading all of the test methods during the inital phase. In this project, the tests are loaded immediately for all assemblies and then stored in a list in RAM.
Please fix the project so it will scale to tens of thousands of tests at least.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a single test project with over 77,000 tests in it. Running the tests on .NET Core using
dotnet test
, these tests are both discovered and complete running within 4 minutes.However, when loading a project that uses
xunit.runner.devices
onMonoAndroid90
(using the Android emulator on Windows 10), it takes about 50 minutes just to discover the tests. Subsequently, the tests will run for over an hour before they crash the runner. Here is the log of the crash:At least for the test discovery part, I noticed that in the
xunit.runner.visualstudio
project is not loading all of the test methods during the inital phase. In this project, the tests are loaded immediately for all assemblies and then stored in a list in RAM.Please fix the project so it will scale to tens of thousands of tests at least.
The text was updated successfully, but these errors were encountered: