2011-06-24 12:27:45 +00:00
|
|
|
* write a 'master' script to run all tests
|
2011-06-27 12:06:41 +00:00
|
|
|
-> work in progress: run_all
|
2011-06-24 12:27:45 +00:00
|
|
|
+ figure out how to store logs and search for interesting
|
|
|
|
|
err/warn keywords spewed up by the script or apps it calls.
|
2011-06-27 12:06:41 +00:00
|
|
|
+ write common configuration facility
|
2011-06-26 13:20:28 +00:00
|
|
|
|
|
|
|
|
* releng_build_isojigdo:
|
|
|
|
|
+ finish boot options
|
2011-06-24 12:27:45 +00:00
|
|
|
|
2011-06-25 16:58:16 +00:00
|
|
|
* releng_check_isocontent: compare input data against the ISO image content, might be tricky
|
2011-06-27 12:06:41 +00:00
|
|
|
-> work in progress
|
|
|
|
|
|
|
|
|
|
* Give up existing standard option -clean in favor of:
|
|
|
|
|
+ Option -keep which keeps the test data from being removed after
|
|
|
|
|
the test.
|
|
|
|
|
+ Option -clean_up which removes the test data without doing another test.
|
|
|
|
|
+ Rule: A test must not overwrite existing data on disk.
|
|
|
|
|
It rather shall refuse and offer option -clean_up to
|
|
|
|
|
solve the problem (after skilled examination by the user).
|
|
|
|
|
+ Rule: A test shall remove all files which it has created.
|
|
|
|
|
Only explicit user orders shall allow test files to persist.
|
|
|
|
|
These orders may be program arguments or configuration variables.
|
|
|
|
|
-> see releng/test_hardlinks for an implementation example
|
|
|
|
|
|
