Overview
Comment: | Updated the documentation |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
e9715ba80fd5dd7ee5fc25eb3c0224d7 |
User & Date: | matt on 2011-05-17 00:59:46 |
Other Links: | manifest | tags |
Context
2011-05-17
| ||
08:31 | Updated the documentation check-in: eec0503d34 user: matt tags: trunk | |
00:59 | Updated the documentation check-in: e9715ba80f user: matt tags: trunk | |
00:58 | Updated the documentation check-in: 3045d5c2b7 user: matt tags: trunk | |
Changes
Modified docs/megatest.html from [7c208fddee] to [e846497271].
︙ | |||
469 470 471 472 473 474 475 | 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 | - - + + | </div> <h2 class="Section"> <a class="toc" name="toc-Section-3.5">3.5</a> Tests with Inter-test dependencies </h2> <div class="Unindented"> Sometimes a test depends on the output from a previous test or it may not make sense to run a test is another test does not complete with status “PASS”. In either of these scenarios you can use the “waiton” keyword in your testconfig file to indicate that this test must wait on one or more tests to complete before being launched. In this example there is no point in running the “system” test if the “cpu” and “mem” tests either do not complete or complete but with status “FAIL”. </div> |
︙ | |||
1379 1380 1381 1382 1383 1384 1385 | 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 | - + | </table> </div> <hr class="footer"/> <div class="footer" id="generated-by"> |
Modified docs/megatest.lyx from [51edb82821] to [153d81297c].
︙ | |||
986 987 988 989 990 991 992 | 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 | - + | FAIL \begin_inset Quotes erd \end_inset . \end_layout |
︙ |