• Home
  • History
  • Annotate
  • only in this directory
NameDateSize

..08-Jun-201437

curlcheck.hH A D10-Jan-20134.2 KiB

Makefile.amH A D11-May-20132.8 KiB

Makefile.inH A D11-May-201361.3 KiB

Makefile.incH A D11-May-20131 KiB

READMEH A D10-Jan-20132.2 KiB

unit1300.cH A D10-Jan-20139.6 KiB

unit1301.cH A D10-Jan-20131.8 KiB

unit1302.cH A D10-Jan-20134.1 KiB

unit1303.cH A D10-Jan-20135.1 KiB

unit1304.cH A D10-Jan-20135 KiB

unit1305.cH A D10-Jan-20133.3 KiB

unit1307.cH A D10-Jan-201312 KiB

unit1308.cH A D10-Jan-20133 KiB

unit1309.cH A D10-Jan-20132.6 KiB

unit1330.cH A D11-May-20131.2 KiB

README

1Unit tests
2==========
3
4The goal is to add tests for *ALL* functions in libcurl. If functions are too
5big and complicated, we should split them into smaller and testable ones.
6
7Build Unit Tests
8================
9
10'./configure --enable-debug' is required for the unit tests to build. To
11enable unit tests, there will be a separate static libcurl built that will be
12used exclusively for linking unit test programs. Just build everything as
13normal, and then you can run the unit test cases as well.
14
15Run Unit Tests
16==============
17
18Unit tests are run as part of the regular test suite. If you have built
19everything to run unit tests, to can do 'make test' at the root level. Or you
20can 'cd tests' and then invoke individual unit tests with ./runtests.pl NNNN
21where NNNN is the specific test number.
22
23Debug Unit Tests
24================
25
26If a specific test fails you will get told. The test case then has output left
27in the log/ subdirectory, but most importantly you can re-run the test again
28using gdb by doing ./runtests.pl -g NNNN. That is, add a -g to make it start
29up gdb and run the same case using that.
30
31Write Unit Tests
32================
33
34We put tests that focus on an area or a specific function into a single C
35source file. The source file should be named 'unitNNNN.c' where NNNN is a
36number that starts with 1300 and you can pick the next free number.
37
38You also need a separate file called tests/data/testNNNN (using the same
39number) that describes your test case. See the test1300 file for inspiration
40and the tests/FILEFORMAT documentation.
41
42For the actual C file, here's a very simple example:
43
44----------------------- start -------------------------------
45#include "curlcheck.h"
46
47#include "a libcurl header.h" /* from the lib dir */
48
49static void unit_setup( void )
50{
51  /* whatever you want done first */
52}
53
54static void unit_stop( void )
55{
56  /* done before shutting down and exiting */
57}
58
59UNITTEST_START
60
61  /* here you start doing things and checking that the results are good */
62
63  fail_unless( size == 0 , "initial size should be zero" );
64  fail_if( head == NULL , "head should not be initiated to NULL" );
65
66  /* you end the test code like this: */
67
68UNITTEST_STOP
69
70----------------------- end -------------------------------
71