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
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# @code-pushup/coverage-plugin
2
2
3
-
**Code PushUp plugin for tracking code coverage.**
3
+
🧪 **Code PushUp plugin for tracking code coverage.** ☂️
4
4
5
5
This plugin allows you to measure and track code coverage on your project.
6
6
@@ -20,8 +20,7 @@ Measured coverage types are mapped to Code PushUp audits in the following way
20
20
21
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.
22
22
23
-
> [!IMPORTANT]
24
-
> Please note that when you define the tool command, you still need to define the paths to the coverage results.
23
+
📌 Please note that when you define the tool command, you still need to define the paths to all relevant coverage results.
25
24
26
25
The configuration will look similarly to the following:
27
26
@@ -34,7 +33,7 @@ Measured coverage types are mapped to Code PushUp audits in the following way
@@ -46,8 +45,7 @@ Measured coverage types are mapped to Code PushUp audits in the following way
46
45
47
46
4. (Optional) Reference audits which you wish to include in custom categories (use `npx code-pushup print-config` to list audits and groups).
48
47
49
-
> [!TIP]
50
-
> Assign weights based on what influence each coverage type should have on the overall category score (assign weight 0 to only include as extra info, without influencing category score).
48
+
💡 Assign weights based on what influence each coverage type should have on the overall category score (assign weight 0 to only include as extra info, without influencing category score).
51
49
52
50
```js
53
51
exportdefault {
@@ -124,7 +122,7 @@ It recognises the following entities:
124
122
The plugin accepts the following parameters:
125
123
126
124
-`coverageType`: An array of types of coverage that you wish to track. Supported values: `function`, `branch`, `line`.
127
-
-`reports`: Array of paths to files with code coverage results. LCOV format is supported for now.
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.
128
126
- (optional) `coverageToolCommand`: If you wish to run your coverage tool to generate the results first, you may define it here.
129
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