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
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,24 +79,23 @@ The above command will generate an opencover report in ```TestResults/coverage.o
79
79
80
80
81
81
You don't necessarily have to use the above example to generate the opencover report. If you have other means of doing this, then that should not cause any problems. You actually don't even need a .NET solution. As long as you can provide a path for the coverage file.
82
+
The path is parsed using [Glob](https://www.npmjs.com/package/glob), and this enables you to use patterns to locate coverage files. Be aware, if more than one file is returned, only the first will be used.
| percentage | The code coverage percentage extracted from the file in the provided path |
99
-
| badge | The badge data as in json format as required by shields.io |
98
+
| badge | The badge data as in json format as required by shields.io |
100
99
101
100
## Example Usage
102
101
Below is a snippet of a typical .NET workflow that will restore dependencies, build solution and run unit tests. After those actions the .NET Code Coverage Badge will be generated and the ```percentage``` printet to the workflow log. If you copy-paste this, be sure to rename the ```<MyProject>``` and adjust tje ```gist-filename```, ```gist-id``` and ```gist-auth-token``` to your configuration.
thrownewError('No code coverage percentage was found in the provided opencover report. Was looking for an xml elemet named Summary with the attribute sequenceCoverage');
0 commit comments