libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Moved todo items from releng/README to releng/TODO

Browse Source
This commit is contained in:
Thomas Schmitt
2011-08-19 06:42:53 +00:00
parent 4c99890da7
commit 3fb9388040
2 changed files with 26 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
releng/README
View File

@ -91,17 +91,6 @@ particular manually executable test scripts.
Currently there are the following tests which should have the attention of
the user or require sysadmin considerations before they are run:
./manual_isojigdo -x ../xorriso/xorriso
Exercises the production of a bootable Debian GNU/Linux image and its Jigdo
files. This test downloads a Debian daily image for i386 of about 70 MB,
extracts its content and composes a new image.
Thus it needs about 250 MB of disk space in releng/releng_generated_data .
This test will only work with GNU xorriso or if libjte was installed already
when libisofs was built. libjte is part of package jigit, version >= 1.18,
available at:
http://www.einval.com/~steve/software/JTE/
For building it you will need gmake (which is default "make" on GNU/Linux).
./manual_devices -x ../xorriso/xorriso [-- [--dev device_file_to_use]
[--priv_cmd 'command [arg [arg ...]]']]
Exercises listing of all accessible optical drives and the examination of
@ -130,6 +119,18 @@ the user or require sysadmin considerations before they are run:
Command and arguments must be single words and be submitted alltogether
as one single argument. On Solaris use: --priv_cmd pfexec
./manual_isojigdo -x ../xorriso/xorriso
Exercises the production of a bootable Debian GNU/Linux image and its Jigdo
files. This test downloads a Debian daily image for i386 of about 70 MB,
extracts its content and composes a new image. Thus it needs about 250 MB
of disk space in releng/releng_generated_data .
This test will only work with GNU xorriso or if libjte was installed already
when libisofs was built. Further it needs the script jigdo-gen-md5-list
and the program jigit-mkimage. All three are part of package jigit,
version >= 1.18, available at:
http://www.einval.com/~steve/software/JTE/
Currently jigit builds only in GNU environments.
Any auto_* script can be run on its own. Some of them demand option -x.
All general options are accepted.
@ -160,7 +161,7 @@ The text output of the automatic tests is recorded in file
Script ./run_all_auto will detect failure of perticular tests and report
lines from the log file which contain problem indicating key words:
NEVER|ABORT|FATAL|FAILURE|MISHAP|SORRY|WARNING|HINT|FAIL|ERROR|WRONG
NEVER,ABORT,FATAL,FAILURE,MISHAP,SORRY,WARNING,HINT,FAIL,ERROR,WRONG
If the program messages in log.run_all_auto do not explain the failure,
please contact mailing list libburn-hackers@pykix.org .
@ -276,18 +277,3 @@ If you plan to introduce a specific option, look at the description of
existing tests whether one of them would match your needs. In that case,
please re-use the name of that existing option.
=============================================================================
TODO:
* ??? Delete debian-testing-i386-businesscard.iso with ./run_all_auto -c
* ??? Have a script ./run_all_manual
* derive a GNU xorriso test suite from libisoburn test suite
* auto_ tests should know whether they work underneath run_all_auto
or whether they run standalone

20
releng/TODO
View File

@ -4,7 +4,7 @@
* Enhance 'auto_isocontent'
Extend it to use some more demanding directory tree.
MD5s should be checked. ACLs and xattr (if we are on Linux).
MD5s should be checked.
All file types as of stat(2) should be tested.
Test various comparisons:
xorriso provides built-in means for comparison:
@ -15,13 +15,19 @@
* Test for wrong CD sizes would need a new test and probably an
automatic CD changer.
* Burning tests - maybe a new 'manual_burning' test?
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.
* Library unit tests - 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 put into
codesamples/ directory and run by auto_cxx or a separate auto_ script.
* ??? Still to decide:
Delete debian-testing-i386-businesscard.iso with ./run_all_auto -c
* ??? Still to decide:
Have a script ./run_all_manual
* derive a GNU xorriso test suite from libisoburn test suite
* auto_ tests should know whether they work underneath run_all_auto
or whether they run standalone