|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
CallbackParamsRunner and the annotation
@WrappedRunner, which
together constitute the
primarily recommended means for developing "CallbackParams" tests
- regardless of whether the test-developer uses the API of
JUnit-4.x or JUnit-3.x.
See:
Description
| Class Summary | |
|---|---|
| BddRunner | |
| CallbackParamsRunner | The recommended strategy for JUnit-integration is to use this Runner implementation, by annotating the test-class with ... |
| EnumRunner | The very simpliest use-case for callback-params is when the parameters are self-contained, i.e. |
| Annotation Types Summary | |
|---|---|
| WrappedRunner | Optional annotation to specify a specific Runner-implementation class, to
which CallbackParamsRunner will hand over the actual test-execution. |
The JUnit-4.x integration - including the runner-class
CallbackParamsRunner and the annotation
@WrappedRunner, which
together constitute the
primarily recommended means for developing "CallbackParams" tests
- regardless of whether the test-developer uses the API of
JUnit-4.x or JUnit-3.x.
CallbackParamsRunner (and
@WrappedRunner) have
been tested for JUnit version 4.4 and later but we believe they will work
fine for any 4.x version.
Another - more experimental - resource in this package is
EnumRunner, which demands
JUnit version 4.5 or later.
CallbackParamsRunner - the recommended way to use
"CallbackParams"
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||