From: Paul Moore <[email protected]> Signed-off-by: Paul Moore <[email protected]> --- SUBMITTING_PATCHES.md | 12 ++++++++++++ 1 file changed, 12 insertions(+)
diff --git a/SUBMITTING_PATCHES.md b/SUBMITTING_PATCHES.md index 61170ea2..c24e1416 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 -- You received this message because you are subscribed to the Google Groups "libseccomp" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
