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
Copy file name to clipboardExpand all lines: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,14 @@ For a workspace using client-side editing, test classes are by default sought in
65
65
66
66
> By setting this at the workspace level you can have different file layouts for different projects.
67
67
68
+
To gather test coverage data you will need at least one `coverage.list` file in your tree of test classes. See the Test Coverage Tool documentation for information about what this file should contain.
69
+
70
+
When using client-side editing your `coverage.list` file(s) must be in or below your `relativeTestRoot` client-side folder.
71
+
72
+
When using server-side editing, put a single `coverage.list` file in the server-side folder named in your ^UnitTestRoot global.
73
+
74
+
If no `coverage.list` file is found during a coverage run then the output in the Test Results tab of the VS Code Panel will include the line `No code coverage found (!)`.
75
+
68
76
## Running Tests
69
77
70
78
VS Code provides several different ways to run tests.
0 commit comments