curl/tests/unit
Daniel Stenberg 84bd19ffd4 timers: fix timer regression involving redirects / reconnects
In commit 0b3750b5c2 (released in 7.36.0) we fixed a timeout issue
but instead broke the timings.

To fix this, I introduce a new timestamp to use for the timeouts and
restored the previous timestamp and timestamp position so that the old
timer functionality is restored.

In addition to that, that change also broke connection timeouts for when
more than one connect was used (as it would then count the total time
from the first connect and not for the most recent one). Now
Curl_timeleft() has been modified so that it checks against different
start times depending on which timeout it checks.

Test 1303 is updated accordingly.

Bug: http://curl.haxx.se/mail/lib-2014-05/0147.html
Reported-by: Ryan Braud
2014-05-15 21:28:19 +02:00
..
.gitignore
curlcheck.h
Makefile.am
Makefile.inc mprintf: allow %.s with data not being zero terminated 2014-05-04 23:39:52 +02:00
README
unit1300.c
unit1301.c
unit1302.c base64: Extended validation to look for invalid characters 2013-12-01 11:12:23 +00:00
unit1303.c timers: fix timer regression involving redirects / reconnects 2014-05-15 21:28:19 +02:00
unit1304.c unit1304: make the test pass the OOM torture tests 2014-01-28 23:47:20 +01:00
unit1305.c unittests: do not include curl_memory.h 2014-01-03 12:30:23 +01:00
unit1307.c
unit1308.c
unit1309.c
unit1330.c
unit1394.c unittests: do not include curl_memory.h 2014-01-03 12:30:23 +01:00
unit1395.c copyright: Updated following recent edits 2014-04-28 23:20:52 +01:00
unit1396.c unit1396: make the test pass the OOM torture tests 2014-01-28 23:27:22 +01:00
unit1397.c test1397: Fixed compilation with some SSL backends 2014-03-26 22:08:53 +01:00
unit1398.c mprintf: allow %.s with data not being zero terminated 2014-05-04 23:39:52 +02:00

Unit tests
==========

The goal is to add tests for *ALL* functions in libcurl. If functions are too
big and complicated, we should split them into smaller and testable ones.

Build Unit Tests
================

'./configure --enable-debug' is required for the unit tests to build. To
enable unit tests, there will be a separate static libcurl built that will be
used exclusively for linking unit test programs. Just build everything as
normal, and then you can run the unit test cases as well.

Run Unit Tests
==============

Unit tests are run as part of the regular test suite. If you have built
everything to run unit tests, to can do 'make test' at the root level. Or you
can 'cd tests' and then invoke individual unit tests with ./runtests.pl NNNN
where NNNN is the specific test number.

Debug Unit Tests
================

If a specific test fails you will get told. The test case then has output left
in the log/ subdirectory, but most importantly you can re-run the test again
using gdb by doing ./runtests.pl -g NNNN. That is, add a -g to make it start
up gdb and run the same case using that.

Write Unit Tests
================

We put tests that focus on an area or a specific function into a single C
source file. The source file should be named 'unitNNNN.c' where NNNN is a
number that starts with 1300 and you can pick the next free number.

You also need a separate file called tests/data/testNNNN (using the same
number) that describes your test case. See the test1300 file for inspiration
and the tests/FILEFORMAT documentation.

For the actual C file, here's a very simple example:

----------------------- start -------------------------------
#include "curlcheck.h"

#include "a libcurl header.h" /* from the lib dir */

static void unit_setup( void )
{
  /* whatever you want done first */
}

static void unit_stop( void )
{
  /* done before shutting down and exiting */
}

UNITTEST_START

  /* here you start doing things and checking that the results are good */

  fail_unless( size == 0 , "initial size should be zero" );
  fail_if( head == NULL , "head should not be initiated to NULL" );

  /* you end the test code like this: */

UNITTEST_STOP

----------------------- end -------------------------------