Skip to content

Commit

Permalink
Add workaround for dotCover coverage reports that are too big (#197)
Browse files Browse the repository at this point in the history
* feature: Add workaround for dotCover reports that are too large

* fix: Format title more consistently with other Troubleshooting sections

* fix: Reword workaround instructions
  • Loading branch information
prcr authored Apr 13, 2020
1 parent 3f84dc6 commit 276bc71
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,16 @@ For a complete list of commands and options: `--help`

## Troubleshooting

### `JsonParseException` while uploading C# coverage data

If you're using dotCover to generate coverage reports for your C# projects, you should [exclude xUnit files](https://www.jetbrains.com/help/dotcover/Running_Coverage_Analysis_from_the_Command_LIne.html#filters_cmd) from the coverage analysis as follows:

```bash
dotCover.exe cover ... /Filters=-:xunit*
```

By default, dotCover includes xUnit files in the coverage analysis and this results in larger coverage reports. This filter helps ensure that the resulting coverage data does not exceed the size limit accepted by the Codacy API when uploading the results.

### `Failed to upload report: Not Found`

Error when running the command, then you'll probably have codacy-coverage-reporter 1.0.3 installed.
Expand Down

0 comments on commit 276bc71

Please sign in to comment.