sigb.us/dendrite
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases 1 Wiki Activity

Explain gb test output (#420)

Browse source 
`gb test`s output is confusing as it is similar to that of `gb build`.
Rather than building, it's actually running all the tests. If no output
past this shows, then all tests have succeeded.

Updates CONTRIBUTING.md to include a note about this.
This commit is contained in:
Andrew Morgan 2018-03-13 03:35:24 -07:00 committed by Richard van der Hoff
parent b72ed3e38c
commit 2ccf9f3a32
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
CONTRIBUTING.md
View file

@ -13,8 +13,10 @@ instance of dendrite, and [CODE_STYLE.md](CODE_STYLE.md) for the code style
guide. guide.
We use `gb` for managing our dependencies, so `gb build` and `gb test` is how We use `gb` for managing our dependencies, so `gb build` and `gb test` is how
to build dendrite and run the unit tests respectively. There are [scripts](scripts) to build dendrite and run the unit tests respectively. Be aware that a list of
for [linting](scripts/find-lint.sh) and doing a [build/test/lint run](scripts/build-test-lint.sh). all dendrite packages is the expected output for all tests succeeding with `gb
test`. There are also [scripts](scripts) for [linting](scripts/find-lint.sh)
and doing a [build/test/lint run](scripts/build-test-lint.sh).
## Picking Things To Do ## Picking Things To Do