|
2 | 2 |
|
3 | 3 | Support for discovering tests and test suites using reflection. |
4 | 4 |
|
5 | | -It follows the xUnit style where each class is a test suite, and each method |
6 | | -with the name prefix "test_" is a single text. |
| 5 | +This package follows the xUnit style where each class is a test suite, and each |
| 6 | +method with the name prefix `test_` is a single test. |
7 | 7 |
|
8 | | -Methods with names starting with "test_" are are run using test() function with |
9 | | -the corresponding name. If the class defines methods setUp() or tearDown(), |
10 | | -they are executed before / after each test correspondingly, even the test fails. |
| 8 | +Methods with names starting with `test_` are run using the `test()` function with |
| 9 | +the corresponding name. If the class defines methods `setUp()` or `tearDown()`, |
| 10 | +they are executed before / after each test correspondingly, even if the test fails. |
11 | 11 |
|
12 | | -Methods with names starting with "solo_test_" are run using solo_test() function. |
| 12 | +Methods with names starting with `solo_test_` are run using the `solo_test()` function. |
13 | 13 |
|
14 | | -Methods with names starting with "fail_" are expected to fail. |
| 14 | +Methods with names starting with `fail_` are expected to fail. |
15 | 15 |
|
16 | | -Methods with names starting with "solo_fail_" are run using solo_test() function |
| 16 | +Methods with names starting with `solo_fail_` are run using the `solo_test()` function |
17 | 17 | and expected to fail. |
18 | 18 |
|
19 | | -Method returning Future class instances are asynchronous, so tearDown() is |
20 | | -executed after the returned Future completes. |
| 19 | +Method returning `Future` class instances are asynchronous, so `tearDown()` is |
| 20 | +executed after the returned `Future` completes. |
21 | 21 |
|
22 | 22 | ## Features and bugs |
23 | 23 |
|
|
0 commit comments