Next: Graphical user interface validation
Up: Acceptance testing
Previous: Building
Command-line interface validation
All commands will be tested for the following:
- A legal command should complete the required action successfully. On
completion, the user interface should indicate the successful completion
of the action.
- Where a command requires a parameter and one is not given, the user
interface should deliver an error message to this effect and not act. The
user interface should tell the user how to obtain a list of valid parameters
interactively.
- Where a command requires a numeric parameter and a non-numeric parameter
is given, the user interface should deliver an error message to this effect
and not act. The user interface should also tell the user the valid numerical
range of the parameter.
- If a command requires a numeric parameter and is given a value that
is out of range, the user interface should deliver an error message to
this effect and not act. The user interface should also tell the user the
valid numerical range of the parameter.
- If a command requires one of a predefined set of of strings and is
given a string outside this set, the user interface should deliver an error
message to this effect and not act. The user interface should also tell
the user the valid values for the parameter.
All commands must conform to any command name conventions provided by
ING during the development process.
All error messages reported by the software system must conform to any
error reporting conventions provided by ING during the development process.
All informational messages reported must conform to any error reporting
conventions provided by ING during the development process.
Fri May 23 10:19:54 BST 1997