3 There are two kinds of tests here: unit tests and shell tests.
7 These go in tests/test_*.c. See the CUT documentation for more info.
9 http://sourceforge.net/projects/cut/
13 Shell tests go in the sh-tests directory and are to be written in pairs:
17 Each .commands file will be nc'd to beanstalkd, and the response diff'd
18 with the appropriate .expected file. If the response is not identical to the
19 .expected file, the test fails. At the moment, the test harness bails upon the
20 first failure, but it could easily be extended to finish the tests and print
23 IMPORTANT: Since beanstalkd expects \r\n line endings, you must be sure to
24 include those in your files. You can tell vim to do this with