Commit 9c97dae
committed
Rediscover tests after a test run
Test projects without code analysis updates (i.e C# projects or projects using Microsoft.Testing.Platform.VSTestBridge)
will show new tests if you run a group of tests that changed, but those new tests will not have code locations.
The lack of code locations in this limited case is very confusing and degrades the experience significantly.
I looked at several options to fill in these locations.
- VSTest does not return test locations on test runs, so mapping a location from results doesn't work
- Running discovery before a test run caused test runs to feel sluggish. Especially when trying to run individual tests, which is a core workflow. I tried project-specific discovery and parallel discovery/test run, but still had an average ~1s delay.
However, test discovery, even with thousands of tests, only takes a few seconds. That feels sluggish before the test run, but is inconsequential after the test run. The discovery is generally finished before the user has evaluated the test results.
This pattern also has some precedent. Visual Studio will generally discover new tests in a group only after you run the group.
Thanks for coming to my ted talk.1 parent 6713384 commit 9c97dae
1 file changed
+3
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1993 | 1993 | | |
1994 | 1994 | | |
1995 | 1995 | | |
1996 | | - | |
| 1996 | + | |
1997 | 1997 | | |
1998 | 1998 | | |
| 1999 | + | |
| 2000 | + | |
1999 | 2001 | | |
2000 | | - | |
2001 | 2002 | | |
2002 | 2003 | | |
2003 | 2004 | | |
| |||
0 commit comments