2011-06-28 17:33:08 +00:00
|
|
|
|
2011-07-18 12:21:39 +00:00
|
|
|
* Merge 'merge_into_isocontent' into 'auto_isocontent' (former hardlinks)
|
2011-07-02 15:28:37 +00:00
|
|
|
Extend it to use some more demanding directory tree.
|
|
|
|
|
MD5s should be checked. ACLs and xattr (if we are on Linux).
|
|
|
|
|
All file types as of stat(2) should be tested.
|
2011-07-07 07:56:44 +00:00
|
|
|
|
2011-07-09 07:33:33 +00:00
|
|
|
* Also check as many as possible trivial operations like:
|
|
|
|
|
xorriso -indev file.iso -pvd_info
|
2011-07-02 15:28:37 +00:00
|
|
|
|
2011-07-18 12:31:23 +00:00
|
|
|
* Burning tests - maybe a new 'manual_burning' test?
|
2011-07-11 19:01:23 +00:00
|
|
|
Further if we want to have a burn test (with MD5 and checkreading)
|
|
|
|
|
then we will need configuration means to enable this. By default
|
|
|
|
|
it should not risk to burn one-time media which sit in the drive
|
|
|
|
|
by mere accident.
|
2011-07-18 07:43:40 +00:00
|
|
|
|
|
|
|
|
* Investigate the possibility to write some cunit-based tests
|
|
|
|
|
(http://cunit.sourceforge.net) for both xorriso.h and libisoburn.h API's.
|
|
|
|
|
The code samples could be dumped into codesamples/ directory and run by
|
2011-07-18 12:21:39 +00:00
|
|
|
auto_cxx or separate auto_ script.
|
2011-07-18 10:33:11 +00:00
|
|
|
|
|
|
|
|
* Try to convert most examples from xorriso(1) manpage into tests.
|
