[Drbd-dev] user interface test of drbd.conf
helmut at wollmersdorfer.at
Wed Oct 20 18:17:27 CEST 2004
I did some systematic test cases with the parameters and options against
the man page.
As we do not have documents like Requirement Definition, Detailed
Functional Specification, Interface Specification (same is true for most
OSS/GPL projects), the documentation is the only source of "promised
Differences between docu and program behaviour mean wrong docu, wrong
program, or both wrong.
Here are some items:
Method: drbdadm -d up all
1) Problem report
| minor-count count
| count may be a number from 1 to 255.
count expected-result test-result
1 valid passed
0 invalid failed
-1 invalid passed
255 valid passed
256 invalid failed
260 invalid failed
Problem description: Parser accepts invalid values.
(assumed) generic requirement: Invalid values should be reported as
error as near as possible to the interface. Invalid values should not
enter a system and cause errors in later steps, or other components, or
in worst case crash the system.
2) Problem report
The sign is important.
Always use a negative value, positive will (try to) force
primary status, which is not what you want, if it has outdated
data. Default is 0, which means unlimited. Unit is seconds.
100000 valid passed
Problem description: Very high, maybe senseless values are accepted.
From my experience as tester I will not expect, that _any_ values will
work correctly without "dry-run". Same is true for other values in
BTW: An appropriate problem tracking system like bugzilla would be nice.
More information about the drbd-dev