File: README

package info (click to toggle)
gnump3d 2.9.3-1sarge3
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 2,420 kB
  • ctags: 366
  • sloc: perl: 10,649; sh: 188; makefile: 147
file content (111 lines) | stat: -rwxr-xr-x 2,277 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111


  GNUMP3d v2.x Test Scripts



About
-----

  This directory contains a collection of test scripts for the
 GNUMP3d v2.x release.

  There is a simple driver program which will call each of the
 tests in turn, and report upon the success or failure of each
 individual test.

  You may choose to run all the scripts at once, or run them
 individually.



Usage
-----

  Usage is fairly straightforward, the runtest script accepts
 the following arguments:


runtests - version 1.5 - http://www.steve.org.uk/

Usage: runtests options [test1] [test2] .. [testN]

Options:
    --all              Run all tests
    --fail             Only display failure messages.
    --version          Show the version number.
    --help             Show this help.



The Tests
---------

  When each test case is run a small description of that test
 will be displayed, which should give a good idea of the area
 of code which is lacking, or on a problem with installation.

  The test scripts themselves are small shell/perl scripts which
 are expected to produce no output and exit with a zero return code
 when successful - and a non-zero exit code when they fail.



Adding A Test
-------------

  The system is designed to be simple to extend, here's an example
 of how to add a test case.


 1.  Create a file with a descriptive title, ensure the filename
    is prefixed with the word 'test'.

 2.  In the first line include the path to the intepretter to be used.

 3.  In the second line include a comment describing what is being
    tested.

 4.  Add test code - with appropriate return values.

 5.  Make the test case executable.


    So, to test the existance of '/etc/passwd' you'd end up with 
  an executable file like this:

--------------
#!/bin/sh
# Test for the presence of the passwd file.

if [ -e /etc/passwd ]; then
   exit 0;
else
   exit 1;
fi
---------------




Notes
-----

  Any file with the name 'test*' will be treated as a test file,
 unless it has a '.data', or '.out' suffix.  These are treated
 as files which may be used for storing expected results - or data
 for the test case itself.



Comments / Feedback?
--------------------

  Comments, feedback, updated test cases, or suggestions would be
 greatfully recieved.



Steve
---
www.steve.org.uk