Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add list of subcommands to README.md #374

Open
wants to merge 27 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update README.md
  • Loading branch information
davehenton authored Nov 12, 2018
commit 8fff54a46509b9cfa3001df8a2923946a043fe34
13 changes: 8 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -2,6 +2,8 @@

# Code Climate Test Reporter

## Overview

Code Climate's test reporter is a binary that works in coordination with codeclimate.com to report test coverage data. Once you've set up test coverage reporting you can:
* view test coverage reports for each file alongside quality metrics like complexity, duplication, and churn,
* toggle between viewing code issues and test coverage line-by-line in the same source listings,
@@ -11,11 +13,13 @@ Code Climate accepts test coverage data from virtually any location, including l

For installation instructions, check out our docs on [Configuring Test Coverage](https://docs.codeclimate.com/docs/configuring-test-coverage) and [Test Coverage Troubleshooting Tips](https://docs.codeclimate.com/docs/test-coverage-troubleshooting-tips).


## Subcommands
Some installations may require the use of the following [subcommands](https://docs.codeclimate.com/docs/configuring-test-coverage#section-list-of-subcommands):



#### `format-coverage` - formats test report from local test suite into generalized format, readable by Code Climate
* `format-coverage` - formats test report from local test suite into generalized format, readable by Code Climate

- `-t` or `--input-type` *simplecov | lcov | coverage.py | gcov | clover* - Identifies the input type (format) of the COVERAGE_FILE

@@ -27,7 +31,7 @@ Some installations may require the use of the following [subcommands](https://do



#### `sum-coverage` - combines test reports from multiple sources (i.e. multiple test suites or parallelized CI builds) into one test report which is readable by Code Climate
* `sum-coverage` - combines test reports from multiple sources (i.e. multiple test suites or parallelized CI builds) into one test report which is readable by Code Climate

- `-o PATH` or `--output PATH` - Output to PATH. If - is given, content will be written to stdout. Defaults to coverage/codeclimate.json.

@@ -38,8 +42,7 @@ Some installations may require the use of the following [subcommands](https://do




#### `upload-coverage` - uploads formatted, singular test report to Code Climate API
* `upload-coverage` - uploads formatted, singular test report to Code Climate API

- `-i PATH` or `--input PATH` - Read payload from PATH. If - is given, the payload will be read from stdin. Defaults to coverage/codeclimate.json.

@@ -49,7 +52,7 @@ Some installations may require the use of the following [subcommands](https://do



#### `after-build` - combines `format-coverage` and `upload-coverage`
* `after-build` - combines `format-coverage` and `upload-coverage`

- `--exit-code $EXIT_CODE` - `$EXIT_CODE` should be the exit code of your test suite process. Some CI system expose this as an environment variable; for others, you may need to manually capture `$?` to provide it to `after-build` later. Providing this will prevent sending test coverage results for failed tests.