Google Git
Sign in
fuchsia / third_party / curl / refs/heads/main / . / tests / unit
tree: cd11c1603ab70267538c48867cd686ae018475f9 [path history] [tgz]
  1. .gitignore
  2. CMakeLists.txt
  3. curlcheck.h
  4. Makefile.am
  5. Makefile.inc
  6. README.md
  7. unit1300.c
  8. unit1302.c
  9. unit1303.c
  10. unit1304.c
  11. unit1305.c
  12. unit1307.c
  13. unit1308.c
  14. unit1309.c
  15. unit1323.c
  16. unit1330.c
  17. unit1394.c
  18. unit1395.c
  19. unit1396.c
  20. unit1397.c
  21. unit1398.c
  22. unit1399.c
  23. unit1600.c
  24. unit1601.c
  25. unit1602.c
  26. unit1603.c
  27. unit1604.c
  28. unit1605.c
  29. unit1606.c
  30. unit1607.c
  31. unit1608.c
  32. unit1609.c
  33. unit1610.c
  34. unit1611.c
  35. unit1612.c
  36. unit1614.c
  37. unit1620.c
  38. unit1621.c
  39. unit1650.c
  40. unit1651.c
  41. unit1652.c
  42. unit1653.c
  43. unit1654.c
  44. unit1655.c
  45. unit1660.c
  46. unit1661.c
  47. unit2600.c
  48. unit2601.c
  49. unit2602.c
  50. unit2603.c
  51. unit3200.c
tests/unit/README.md

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 make 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 %LOGDIR 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 previously unused number.

Add your test to tests/unit/Makefile.inc (if it is a unit test). Add your test data file name to tests/data/Makefile.inc

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.md documentation.

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


    #include "curlcheck.h"

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

    static CURLcode unit_setup( void )
    {
      /* whatever you want done first */
      return CURLE_OK;
    }

    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