• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

.gitignoreD22-Nov-202321 21

Makefile.amD22-Nov-20233.1 KiB7934

Makefile.incD22-Nov-20231.9 KiB6945

READMED22-Nov-20232.2 KiB7149

curlcheck.hD22-Nov-20234.4 KiB10161

unit1300.cD22-Nov-20239.6 KiB293136

unit1301.cD22-Nov-20231.8 KiB5521

unit1302.cD22-Nov-20235.6 KiB158108

unit1303.cD22-Nov-20235.2 KiB14779

unit1304.cD22-Nov-20236.7 KiB186112

unit1305.cD22-Nov-20233.3 KiB14290

unit1307.cD22-Nov-202312 KiB235184

unit1308.cD22-Nov-20233 KiB9648

unit1309.cD22-Nov-20232.6 KiB11163

unit1330.cD22-Nov-20231.2 KiB4213

unit1394.cD22-Nov-20234.4 KiB12391

unit1395.cD22-Nov-20232.4 KiB8551

unit1396.cD22-Nov-20233.1 KiB11275

unit1397.cD22-Nov-20232 KiB5235

unit1398.cD22-Nov-20233.2 KiB9242

unit1600.cD22-Nov-20232.3 KiB6430

unit1601.cD22-Nov-20231.6 KiB5219

unit1602.cD22-Nov-20232 KiB8141

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