Writing Shell Tests: Difference between revisions
From SambaWiki
(shell based testing) |
(explain that python can do blackbox tests) |
||
| Line 3: | Line 3: | ||
==Avoid writing new shell-based tests== |
==Avoid writing new shell-based tests== |
||
New tests should be written in [[Writing_Python_Tests|Python]] |
New tests should be written in [[Writing_Python_Tests|Python]]. |
||
This includes [[Writing_Python_Tests#Testing_Samba_binaries|Black-box tests of Samba binaries]] using '''samba.tests.BlackboxTestCase'''. |
|||
==Avoid bashisms== |
==Avoid bashisms== |
||
Revision as of 06:22, 2 August 2017
Writing shell tests
Avoid writing new shell-based tests
New tests should be written in Python.
This includes Black-box tests of Samba binaries using samba.tests.BlackboxTestCase.
Avoid bashisms
On many systems (Debian and Ubuntu in particular)
/bin/sh
is actually *dash* not *bash*. Therefore avoid bash specific syntax.
Use helper functions
If your test is in testprogs/blackbox you can use:
. `dirname $0`/subunit.sh . `dirname $0`/common_test_fns.inc
otherwise you will need to use a ../ path to find these.
testit
testit is the primary test command, testing one particular command for success.
testit "change dc password" $samba4srcdir/scripting/devel/chgtdcpass -s $PROVDIR/etc/smb.conf || failed=`expr $failed + 1`
exit code
The script should exit with the number of failures
exit $failed