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
Creating a class with 65k tests (limit of max methods per class is just a smidge above that), results in the run being really slow.
Class with 10k empty tests runs in about 4 seconds. (Even if there are 9999 filters).
Class with 65k tests run over 4 minutes.
This does not seem to be related to filtering, it takes this long even without any filters applied.
I did not check if this happens if the total amount of tests are over a given limit. Single class with more than 10k tests is unlikely, but run with 20k tests in total is not as unlikely.
Added to sprint for quick test if someone can see what is going on. We mostly should optimize for test runs of 1-100 tests, and discovery of 10-1000 tests, so this is quite a bit out of that scope, but still might be worth it if obvious problem is found.
Creating a class with 65k tests (limit of max methods per class is just a smidge above that), results in the run being really slow.
Class with 10k empty tests runs in about 4 seconds. (Even if there are 9999 filters).
Class with 65k tests run over 4 minutes.
This does not seem to be related to filtering, it takes this long even without any filters applied.
I did not check if this happens if the total amount of tests are over a given limit. Single class with more than 10k tests is unlikely, but run with 20k tests in total is not as unlikely.
AB#1865125
The text was updated successfully, but these errors were encountered: