1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-22 13:34:15 +03:00
samba-mirror/selftest
Jeremy Allison 937d35bd18 s4: torture : Add test case to show that a bad impersonation level causes an error on a regular file open.
An invalid impersonation level is only allowed for durable handle reopen.

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Ira Cooper <ira@samba.org>

Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Wed Jun 18 09:42:43 CEST 2014 on sn-devel-104
2014-06-18 09:42:42 +02:00
..
target s4-winbind: Use winbindd in the AD DC for fl2003dc and plugin_s4_dc 2014-06-16 02:53:48 +02:00
tests selftest: fix use of a non-existent word (existant) 2012-06-12 07:21:43 +02:00
__init__.py selftest.py: Add dummy init file (required to run tests). 2012-03-04 18:02:07 +01:00
client.py selfclient.client: Factor out write_clientconf. 2012-03-05 03:45:57 +01:00
devel_env.sh selftest: Add a bash env file you can source. 2014-04-17 14:56:05 +02:00
filter-subunit selftest: Place the test environment at the end of the failure lines 2012-04-27 14:51:05 +02:00
flapping selftest: Remove samba3.smb2.lock.*.rw-exclusive from flapping file 2013-12-06 05:19:37 +01:00
format-subunit format-subunit: Split out summary file writing. 2010-10-02 18:40:44 +02:00
gdb_backtrace selftest: Cope with no binary argument being supplied to gdb_backtrace 2011-06-24 13:17:19 +10:00
gdb_backtrace_test.c selftest: Fix typo in comment. 2010-06-01 09:45:19 +02:00
gdb_run
in_screen selftest: Add support for tmate. 2014-06-06 02:25:52 +02:00
knownfail s4: torture : Add test case to show that a bad impersonation level causes an error on a regular file open. 2014-06-18 09:42:42 +02:00
quick selftest: Have only one set of selftest knownfail and skip files 2011-10-28 13:10:27 +02:00
README selftest/README: Expand inconsistent tabs 2012-03-04 01:20:03 +01:00
run.py selftest.run: Use subunit version of iso8601. 2012-03-12 01:36:25 +01:00
selftest.pl selftest: Set winbind separator = / 2014-06-04 03:22:25 +02:00
selftest.pl.1 selftest: Move manual page into a separate file. 2012-03-02 03:49:09 +01:00
selftest.py selftest: use MALLOC_CHECK_=3 to give a diagnostic on failure 2013-12-11 17:14:50 +01:00
selftesthelpers.py selftest: Remove print_smbtorture4_version and smbtorture4_possible check 2014-03-26 04:20:16 +01:00
skip selftest: skip GETADDRINFO tests 2014-05-09 19:28:13 +02:00
slow selftest: Have only one set of selftest knownfail and skip files 2011-10-28 13:10:27 +02:00
socket_wrapper.py selftest.socket_wrapper: interface is an integer. 2012-03-04 18:02:06 +01:00
SocketWrapper.pm
Subunit.pm selftest: Let tests add prefix to tests by themselve. 2010-09-22 17:48:23 -07:00
subunithelper.py selftest/subunithelper.py: correctly pass testsuite-uxsuccess to end_testsuite() 2014-03-13 23:49:35 +01:00
testlist.py selftest.run: Factor out read_testlist_file and open_file_or_pipe. 2012-03-05 05:42:19 +01:00
tests.py selftest: Add tests for dbcheck detection and removal of partial objects 2014-05-03 07:57:13 +02:00
TODO
valgrind_run selftest: set valgrind options 2013-12-11 17:14:21 +01:00
wscript selftest: Preload socket_wrapper. 2014-04-17 14:56:06 +02:00

# vim: ft=rst

This directory contains test scripts that are useful for running a
bunch of tests all at once. 

There are two parts to this: 

 * The test runner (selftest/selftest.pl)
 * The test formatter

selftest.pl simply outputs subunit, which can then be formatted or analyzed 
by tools that understand the subunit protocol. One of these tools is 
format-subunit, which is used by default as part of "make test".

Available testsuites
====================
The available testsuites are obtained from a script, usually 
source{3,4}/selftest/tests.py. This script should for each testsuite output
the name of the test, the command to run and the environment that should be 
provided. Use the included "plantest" function to generate the required output.

Testsuite behaviour
===================

Exit code
------------
The testsuites should exit with a non-zero exit code if at least one 
test failed. Skipped tests should not influence the exit code.

Output format
-------------
Testsuites can simply use the exit code to indicate whether all of their 
tests have succeeded or one or more have failed. It is also possible to 
provide more granular information using the Subunit protocol. 

This protocol works by writing simple messages to standard output. Any 
messages that can not be interpreted by this protocol are considered comments 
for the last announced test.

For a full description of the subunit protocol, see ../lib/subunit/README.

The following commands are Samba extensions to Subunit:

testsuite-count
~~~~~~~~~~~~~~~
testsuite-count: number

Announce the number of tests that is going to be run.

start-testsuite
~~~~~~~~~~~~~~~
start-testsuite: name

The testsuite name is used as prefix for all containing tests.

skip-testsuite
~~~~~~~~~~~~~~
skip-testsuite: name

Mark the testsuite with the specified name as skipped.

testsuite-success
~~~~~~~~~~~~~~~~~
testsuite-success: name

Indicate that the testsuite has succeeded successfully.

testsuite-fail
~~~~~~~~~~~~~~
testsuite-fail: name

Indicate that a testsuite has failed.

Environments
============
Tests often need to run against a server with particular things set up, 
a "environment". This environment is provided by the test "target": Samba 3, 
Samba 4 or Windows.

The environments are currently available include

 - none: No server set up, no variables set.
 - dc,s3dc: Domain controller set up. The following environment variables will
   be set:

     * USERNAME: Administrator user name
     * PASSWORD: Administrator password
     * DOMAIN: Domain name
     * REALM: Realm name
     * SERVER: DC host name 
     * SERVER_IP: DC IPv4 address
     * NETBIOSNAME: DC NetBIOS name
     * NETIOSALIAS: DC NetBIOS alias

 - member,s4member,s3member: Domain controller and member server that is joined to it set up. The
   following environment variables will be set:

     * USERNAME: Domain administrator user name
     * PASSWORD: Domain administrator password
     * DOMAIN: Domain name
     * REALM: Realm name
     * SERVER: Name of the member server

See Samba.pm, Samba3.pm and Samba4.pm for the full list.

Running tests
=============

To run all the tests use::

   make test

To run a quicker subset run::

   make quicktest

To run a specific test, use this syntax::

   make test TESTS=testname

for example::

   make test TESTS=samba4.BASE-DELETE