Changeset 4addf74 in mod_gnutls for test/README


Ignore:
Timestamp:
Aug 22, 2015, 3:30:24 PM (5 years ago)
Author:
Daniel Kahn Gillmor <dkg@…>
Branches:
debian/master, debian/stretch-backports, jessie-backports, upstream
Children:
71e9a5c, 89f863f
Parents:
ae29683 (diff), a1c4c2d (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Imported Upstream version 0.7

File:
1 moved

Legend:

Unmodified
Added
Removed
  • test/README

    rae29683 r4addf74  
    22==================================
    33
    4 Initial Author: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
     4Authors: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
     5         Thomas Klute <thomas2.klute@uni-dortmund.de>
    56
    67There are a lot of ways that a TLS-capable web server can go wrong.  I
     
    1112=================
    1213
    13 from the top level of the source, just run:
     14from the top level of the source, or from test/ (where this README is),
     15just run:
    1416
    1517 make check
    1618
    17 from t/ (where this README is), just run:
     19from test/ you can also run specific tests by passing their script
     20names to make in the TESTS variable:
    1821
    19  make
    20 
    21 also from t/ you can also run specific tests (identified by number)
    22 with:
    23 
    24  make t-3
     22 TESTS="test-03_cachetimeout_in_vhost.bash" make -e check
    2523
    2624This should be handy when you're just trying to experiment with a new
    2725test and don't want to wait for the full test suite to run.
    2826
     27The default configuration assumes that an IPv6 loopback device is
     28available (TEST_IP=[::1]) and that TEST_HOST="localhost" resolves to
     29the IPv6 loopback address [::1]. If this does not apply to your
     30system, you can pass different values to ./configure, e.g. to use IPv4
     31instead:
     32
     33  TEST_HOST="localhost" TEST_IP="127.0.0.1" ./configure
    2934
    3035Adding a Test
     
    3338Please add more tests!
    3439
    35 The simplest way to add a test is (from t/):
     40The simplest way to add a test is (from test/):
    3641
    3742 ./newtest
    3843
    39 This will prompt you for a simple name for the test and then copy a starting
    40 set of files from tests/00_basic.
     44This will prompt you for a simple name for the test and then copy a
     45starting set of files from tests/00_basic, and create a script which
     46you can add to TESTS in Makefile.am when your test is ready for
     47inclusion in the test suite.
    4148
    4249
     
    4451==============
    4552
    46 Each test consists of a directory in t/tests/, which will cause the
     53Each test consists of a directory in test/tests/, which will cause the
    4754test suite to spin up an isolated apache instance and try to connect
    4855to it with gnutls-cli and make a simple HTTP 1.1 request.
     
    8289check" to adjust them):
    8390
    84  * they need a functioning loopback device and expect (by default) to
    85    have IPv6 functionality. [TEST_IP]
     91 * they need a functioning loopback device.
    8692
    87  * they expect (by default) the IPv6 loopback to have port 9932
     93 * they expect (by default) the TEST_IP to have port 9932
    8894   open. [TEST_PORT]
    8995
     
    9298   reasons. [TEST_QUERY_DELAY (seconds for the http request to be sent
    9399   and responded to)] and [TEST_GAP (seconds to wait between tests)]
    94 
    95  * they assume that the name "localhost" is associated with the IPv6
    96    loopback address [TEST_HOST]
Note: See TracChangeset for help on using the changeset viewer.