Request is an abstract description of tests to be run. Older versions of
JUnit did not need such a concept--tests to be run were described either by classes containing
tests or a tree of Tests. However, we want to support filtering and sorting,
so we need a more abstract specification than the tests themselves and a richer
specification than just the classes.
The flow when JUnit runs tests is that a Request specifies some tests to be run ->
a Runner is created for each class implied by the Request -> the Runner
returns a detailed Description which is a tree structure of the tests to be run.
| Constructor Summary |
|---|
|
No description provided. |
| Method Summary | |
|---|---|
| static Request |
Create a Request that, when processed, will run all the tests
in a class.
|
| static Request |
Create a Request that, when processed, will run all the tests
in a set of classes.
|
| static Request |
No description provided. |
| Request |
No description provided. |
| Request |
No description provided. |
| Runner |
No description provided. |
| static Request |
Create a Request that, when processed, will run a single test.
|
| Request |
No description provided. |
| Methods inherited from java.langObject |
|---|
Request that, when processed, will run all the tests
in a class. The odd name is necessary because class is a reserved word. Request that, when processed, will run all the tests
in a set of classes. Request that, when processed, will run a single test.
This is done by filtering out all other tests. This method is used to support rerunning
single tests.