commit 1a2aa4e3f8628e5d1343414e0034d2136ad26672 Author: Chelsea H. Komlo chelsea.komlo@gmail.com Date: Fri Oct 14 10:27:21 2016 -0400
adding instructions how to include new test files --- doc/HACKING/WritingTests.md | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/doc/HACKING/WritingTests.md b/doc/HACKING/WritingTests.md index 7bcadc6..de80bbd 100644 --- a/doc/HACKING/WritingTests.md +++ b/doc/HACKING/WritingTests.md @@ -152,6 +152,11 @@ or create a new C file there. Each test is a single function that must be indexed in the table at the end of the file. We use the label "done:" as a cleanup point for all test functions.
+If you have created a new test file, you will need to: +1. Add the new test file to include.am +2. In `test.h`, include the new test cases (testcase_t) +3. In `test.c`, add the new test cases to testgroup_t testgroups + (Make sure you read `tinytest-manual.md` before proceeding.)
I use the term "unit test" and "regression tests" very sloppily here.
tor-commits@lists.torproject.org