B | |
| build_diagnostic [TestBuilder] |
Utility function to handle building diagnostic nodes
|
| build_diagnostic_message [TestBuilder] |
this builds a simpler diagnostic message
|
| build_extended_diagnostic_message [TestBuilder] |
This builds an extended diagnostic message,
showing the values gotten and the
values that were expected.
|
| build_test_case [TestBuilder] |
This builds a simple tests case.
|
C | |
| count_test_failures [TAPDocument] | |
| count_test_nodes [TAPDocument] | |
| count_tests [TAPDocument] | |
| create_count_footer [TAPDocument] | |
| create_failure_footer [TAPDocument] | |
| create_test_plan [TestBuilder] |
This initalizes the test plan.
|
D | |
| diag [TestSimple] |
Occassionally it is useful to print out random diagnostic messages within
your test suite, either for debugging or some other purpose.
|
I | |
| init_document [TAPDocument] |
After constructing a document, you must initialize it
to assure that it has all the correct footers.
|
| is [TestSimple] |
This is similar to the
ok test except that it takes two values and performs
it's own comparison on them using =.
|
N | |
| no_plan [TestSimple] |
On occasion you do not know the number of tests in advance, in such cases
it is possible to not specify a plan.
|
| no_plan [TestBuilder.Tester] |
This replaces
TestSimple.no_plan but returns
a string rather then printing to stdout
|
O | |
| ok [TestSimple] |
An
ok tests is the most basic test, it is similar to assert in that
it expects a boolean value, or an expression which reduces to a boolean,
as it's basic test.
|
P | |
| plan [TestSimple] |
Simply pass
plan the number of tests you plan to run, like so:
|
| plan [TestBuilder.Tester] |
This replaces
TestSimple.plan but returns
a string rather then printing to stdout
|
S | |
| string_of_diagnostic [TAPDocument] | |
| string_of_directive [TAPDocument] | |
| string_of_document [TAPDocument] | |
| string_of_node [TAPDocument] | |
| string_of_status [TAPDocument] |