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: packages/plugin-coverage/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,8 @@ Measured coverage types are mapped to Code PushUp audits in the following way
18
18
19
19
3. Add this plugin to the `plugins` array in your Code PushUp CLI config file (e.g. `code-pushup.config.js`).
20
20
21
-
Pass coverage types you wish to track (line, branch or function), paths to the code coverage results in LCOV format and optionally define your code coverage tool to be run first.
21
+
Pass paths to the code coverage results in LCOV format and optionally define your code coverage tool to be run first.
22
+
All coverage types are measured by default. If you wish to focus on a subset of offered types of coverage, define them in `coverageTypes`.
22
23
23
24
📌 Please note that when you define the tool command, you still need to define the paths to all relevant coverage results.
24
25
@@ -32,7 +33,6 @@ Measured coverage types are mapped to Code PushUp audits in the following way
@@ -121,7 +121,7 @@ It recognises the following entities:
121
121
122
122
The plugin accepts the following parameters:
123
123
124
-
-`coverageType`: An array of types of coverage that you wish to track. Supported values: `function`, `branch`, `line`.
124
+
-`coverageTypes`: An array of types of coverage that you wish to track. Supported values: `function`, `branch`, `line`. Defaults to all available types.
125
125
-`reports`: Array of information about files with code coverage results - paths to results, path to project root the results belong to. LCOV format is supported for now.
126
126
- (optional) `coverageToolCommand`: If you wish to run your coverage tool to generate the results first, you may define it here.
127
127
- (optional) `perfectScoreThreshold`: If your coverage goal is not 100%, you may define it here in range 0-1. Any score above the defined threshold will be given the perfect score. The value will stay unaffected.
0 commit comments