Difference between revisions of "Samba4/Tests"

 
 
(15 intermediate revisions by one other user not shown)
Line 1: Line 1:
Since Samba4 is a test-driven development process, the roadmap here follows that model. A list of tests used in Samba4 development follows below. You can get an idea of where Samba4 development currently stands, as well as an idea of how much work has been done, by the Pass/Fail marks alongside each test.
+
Test coverage information (regularly updated) can be found here:
 +
 
 +
* http://build.samba.org/lcov/data/magni/samba_4_0_test/
 +
 
 +
Areas which need improvements wrt tests:
 +
 
 +
* wins
 +
* tls
 +
* upgrade
 +
* dsdb
 +
* client
 +
* ctdb
 +
* lib/compression
 +
* lib/socket/access.c
 +
* lib/socket_wrapper
 +
* libcli/dgram
 +
* nbt_server/dgram
 +
* rpc_server/drsuapi
 +
* rpc_server/epmapper
 +
* rpc_server/remote
 +
* rpc_server/wkssvc
 +
* web_server/
 +
* winbind
 +
 
 +
Blackbox tests:
 +
* nmblookup
 +
 
 +
I'd also like to parse what tests have failed and what have succeeded in the build farm, so we can show a summary of what tests fail on the main build farm page.
 +
 
 +
== Test environments ==
 +
 
 +
Currently supported test environments:
 +
 
 +
* dc - A standalone Samba 4 DC
 +
* none - Nothing set up (used for local tests)
 +
* member - Samba4 DC with domain member joined to it
 +
 
 +
== Run the testsuite with GDB ==
 +
 
 +
* make test GDBTEST=1
 +
* ../buildtools/bin/waf test --quicktest --gdbtest
 +
 
 +
For other options see selftest/wscript file and assign values to dest keywords

Latest revision as of 17:16, 3 May 2010

Test coverage information (regularly updated) can be found here:

Areas which need improvements wrt tests:

  • wins
  • tls
  • upgrade
  • dsdb
  • client
  • ctdb
  • lib/compression
  • lib/socket/access.c
  • lib/socket_wrapper
  • libcli/dgram
  • nbt_server/dgram
  • rpc_server/drsuapi
  • rpc_server/epmapper
  • rpc_server/remote
  • rpc_server/wkssvc
  • web_server/
  • winbind

Blackbox tests:

  • nmblookup

I'd also like to parse what tests have failed and what have succeeded in the build farm, so we can show a summary of what tests fail on the main build farm page.

Test environments

Currently supported test environments:

  • dc - A standalone Samba 4 DC
  • none - Nothing set up (used for local tests)
  • member - Samba4 DC with domain member joined to it

Run the testsuite with GDB

  • make test GDBTEST=1
  • ../buildtools/bin/waf test --quicktest --gdbtest

For other options see selftest/wscript file and assign values to dest keywords