3 This directory contains test scripts that are useful for running a
4 bunch of tests all at once.
6 There are two parts to this:
8 * The test runner (selftest/selftest.pl)
11 selftest.pl simply outputs subunit, which can then be formatted or analyzed
12 by tools that understand the subunit protocol. One of these tools is
13 format-subunit, which is used by default as part of "make test".
17 The available testsuites are obtained from a script, usually
18 source{3,4}/selftest/tests.py. This script should for each testsuite output
19 the name of the test, the command to run and the environment that should be
20 provided. Use the included "plantest" function to generate the required output.
27 The testsuites should exit with a non-zero exit code if at least one
28 test failed. Skipped tests should not influence the exit code.
32 Testsuites can simply use the exit code to indicate whether all of their
33 tests have succeeded or one or more have failed. It is also possible to
34 provide more granular information using the Subunit protocol.
36 This protocol works by writing simple messages to standard output. Any
37 messages that can not be interpreted by this protocol are considered comments
38 for the last announced test.
40 For a full description of the subunit protocol, see the README file in the subunit
41 repository at http://github.com/testing-cabal/subunit.
43 The following commands are Samba extensions to Subunit:
47 testsuite-count: number
49 Announce the number of tests that is going to be run.
55 The testsuite name is used as prefix for all containing tests.
61 Mark the testsuite with the specified name as skipped.
65 testsuite-success: name
67 Indicate that the testsuite has succeeded successfully.
73 Indicate that a testsuite has failed.
77 Tests often need to run against a server with particular things set up,
78 a "environment". This environment is provided by the test "target": Samba 3,
81 The environments are currently available include
83 - none: No server set up, no variables set.
84 - dc,s3dc: Domain controller set up. The following environment variables will
87 * USERNAME: Administrator user name
88 * PASSWORD: Administrator password
91 * SERVER: DC host name
92 * SERVER_IP: DC IPv4 address
93 * SERVER_IPV6: DC IPv6 address
94 * NETBIOSNAME: DC NetBIOS name
95 * NETIOSALIAS: DC NetBIOS alias
97 - member,s4member,s3member: Domain controller and member server that is joined to it set up. The
98 following environment variables will be set:
100 * USERNAME: Domain administrator user name
101 * PASSWORD: Domain administrator password
102 * DOMAIN: Domain name
104 * SERVER: Name of the member server
106 See Samba.pm, Samba3.pm and Samba4.pm for the full list.
111 To run all the tests use::
115 To run a quicker subset run::
119 To run a specific test, use this syntax::
121 make test TESTS=testname
125 make test TESTS=samba4.BASE-DELETE