| 23 |
|
* <ol> |
| 24 |
|
* |
| 25 |
|
* <li> All assertions in code running in generated threads must use |
| 26 |
< |
* the forms {@link threadFail} , {@link threadAssertTrue} {@link |
| 27 |
< |
* threadAssertEquals}, or {@link threadAssertNull}, (not |
| 26 |
> |
* the forms {@link #threadFail} , {@link #threadAssertTrue} {@link |
| 27 |
> |
* #threadAssertEquals}, or {@link #threadAssertNull}, (not |
| 28 |
|
* <tt>fail</tt>, <tt>assertTrue</tt>, etc.) It is OK (but not |
| 29 |
|
* particularly recommended) for other code to use these forms too. |
| 30 |
|
* Only the most typically used JUnit assertion methods are defined |
| 31 |
|
* this way, but enough to live with.</li> |
| 32 |
|
* |
| 33 |
< |
* <li> If you override {@link setUp} or {@link tearDown}, make sure |
| 33 |
> |
* <li> If you override {@link #setUp} or {@link #tearDown}, make sure |
| 34 |
|
* to invoke <tt>super.setUp</tt> and <tt>super.tearDown</tt> within |
| 35 |
|
* them. These methods are used to clear and check for thread |
| 36 |
|
* assertion failures.</li> |
| 161 |
|
* be reimplemented to use for example a Property. |
| 162 |
|
*/ |
| 163 |
|
protected long getShortDelay() { |
| 164 |
< |
return 100; |
| 164 |
> |
return 10; |
| 165 |
|
} |
| 166 |
|
|
| 167 |
|
|
