diff options
| author | Chelsea H. Komlo <chelsea.komlo@gmail.com> | 2016-10-28 20:20:40 -0500 |
|---|---|---|
| committer | Chelsea H. Komlo <chelsea.komlo@gmail.com> | 2016-12-21 09:44:44 -0500 |
| commit | 064b1b6d1c2beca282dd878e7fa869d1dff1eea3 (patch) | |
| tree | 07838f944e9f4bd14341972f7a9ed91efacfabbd | |
| parent | df87812b41abccd63eab97bd81b476ce61e16f26 (diff) | |
| download | tor-064b1b6d1c2beca282dd878e7fa869d1dff1eea3.tar.gz tor-064b1b6d1c2beca282dd878e7fa869d1dff1eea3.zip | |
Adds standard to run code changes against test suite
| -rw-r--r-- | doc/HACKING/CodingStandards.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md index 01212a9919..009047d6a3 100644 --- a/doc/HACKING/CodingStandards.md +++ b/doc/HACKING/CodingStandards.md @@ -7,6 +7,7 @@ tl;dr: - Run `make check-spaces` to catch whitespace errors - Document your functions - Write unit tests + - Run `make test-full` to test against all unit and integration tests. - Add a file in `changes` for your branch. Patch checklist @@ -26,6 +27,8 @@ Did you remember... - To run `make check-docs` to see whether all new options are on the manpage? - To write unit tests, as possible? + - To run `make test-full` to test against all unit and integration tests (or + `make test-full-online` if you have a working connection to the internet)? - To base your code on the appropriate branch? - To include a file in the `changes` directory as appropriate? |