29 lines
1.1 KiB
Plaintext
29 lines
1.1 KiB
Plaintext
|
Release Engineering
|
||
|
|
~~~~~~~~~~~~~~~~~~~
|
||
|
|
* SOFTWARE TO TEST
|
||
|
|
Use latest libraries code base from svn and bzr
|
||
|
|
(see README for aditional and autodetected library dependencies)
|
||
|
|
Alternatively, use latest all-in-one development tarball from:
|
||
|
|
http://www.gnu.org/software/xorriso/
|
||
|
|
|
||
|
|
* SETUP THE TEST ENVIRONMENT
|
||
|
|
+ Not all TESTs are scripts (e.g. cppcheck, valgrind)
|
||
|
|
+ Copy all FILE.conf.template to $HOME/.libburnia-releng/FILE.conf
|
||
|
|
+ Read the configuration files and set up accordingly to your needs
|
||
|
|
|
||
|
|
* DELIVERING A NEW TEST SCRIPT
|
||
|
|
+ start a new test script over the top of template_new_releng
|
||
|
|
+ all filenames start with releng_ prefix
|
||
|
|
+ self generated data are to be stored in
|
||
|
|
./releng_generated_data/scriptname/ directory
|
||
|
|
+ test data generation options -rc [-keep]
|
||
|
|
+ test data removal options -cleanup
|
||
|
|
+ well documented configuration file $script.conf.template
|
||
|
|
+ throw FAIL string to stdout if any failure is detected
|
||
|
|
+ exit code 0 on success, non-zero on failure
|
||
|
|
+ use different exit codes for any failure (range 1-31)
|
||
|
|
|
||
|
|
* RUNNING TESTS
|
||
|
|
+ All tests have to be run from the releng/ directory, within
|
||
|
|
libisoburn source tree.
|