diff options
| author | Paul Moore <paul@paul-moore.com> | 2017-02-28 15:16:33 -0500 |
|---|---|---|
| committer | Paul Moore <paul@paul-moore.com> | 2017-02-28 15:16:33 -0500 |
| commit | a6c2af564633bc3b44ae89b6a0a8aa9d719b43a7 (patch) | |
| tree | 0e8182db67a34820566ea67bcd9bd52e33b6f9ca | |
| parent | 2d0e0e04654c7fc1cf1a6a49b5db9db6ba23b000 (diff) | |
| download | libseccomp-a6c2af564633bc3b44ae89b6a0a8aa9d719b43a7.tar.gz | |
doc: add a note about writing new tests in SUBMITTING_PATCHES
Signed-off-by: Paul Moore <paul@paul-moore.com>
| -rw-r--r-- | SUBMITTING_PATCHES.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/SUBMITTING_PATCHES.md b/SUBMITTING_PATCHES.md index 61170ea..c24e141 100644 --- a/SUBMITTING_PATCHES.md +++ b/SUBMITTING_PATCHES.md @@ -38,6 +38,18 @@ command: ... if there are any faults or errors they will be displayed. +## Make Sure Your Code is Tested + +The libseccomp code includes a fairly extensive test suite and any submissions +which add functionality or significantly change the existing code should +include additional tests to verify the proper operation of the proposed +changes. + +Code coverage analysis tools has been integrated into the libseccomp code base, +and can be enabled via the "--enable-code-coverage" configure flag and the +"check-code-coverage" make target. Additional details on generating code +coverage information can be found in the .travis.yml file. + ## Generate the Patch(es) Depending on how you decided to work with the libseccomp code base and what |