Blame WritingTests

Karanbir Singh 43deec
Steve Barnes 464547
This file provides guidance on things to bear in mind when writing test scripts for the QA process:
Steve Barnes 464547
Steve Barnes 464547
(a) scripts should exit with either zero to signal success, or non-zero to signal a failure. A failure exit code causes the entire test script execution process to stop (which is fine - we need to see what failed)
Steve Barnes 464547
Steve Barnes 464547
(b) several helper functions are available in test/0_lib/* that should be used in preference to directly calling the commands they implement. Some of the reasons for doing this are consistency in debug output and avoiding timing related test failures. Please review the functions so you're familiar with their existence/operation.
Steve Barnes 464547
Steve Barnes 464547
(c) all test scripts should first make a call to t_Log, passing in $0 and a description of what the test is doing, something like:
Steve Barnes 464547
Steve Barnes 09d4e5
        t_Log "Running $0 - Postfix SMTP test."
Steve Barnes 464547
Steve Barnes 464547
(d) test scripts are processed in alphabetical order, so it's best to install any required packages in a 0-install-blah.sh script. Anything starting with a _ is ignored, and so are files named `readme` (case insensitive)
Steve Barnes 09d4e5
Steve Barnes 09d4e5
(e) all test scripts must be chmod +x in order to be executed. Equally, removing execute permissions from a script will prevent it from being run (or prefixing it with an _, both approaches work)
Steve Barnes 09d4e5
Steve Barnes 09d4e5