See: Description
Class | Description |
---|---|
GeneratedFlowExecutionKey |
A simple flow execution key implementation.
|
MockAction |
A trivial stub action implementation that can be parameterized to return a particular action execution result.
|
MockExternalContext |
Mock implementation of the
ExternalContext interface. |
MockFlowBuilderContext |
A stub flow service locator implementation suitable for a test environment.
|
MockFlowExecutionContext |
A stub implementation of the flow execution context interface.
|
MockFlowExecutionKey |
A simple flow execution key implementation.
|
MockFlowExecutionKeyFactory |
Trivial flow execution key factory implementation that returns a mock flow execution key each time.
|
MockFlowSession |
Mock implementation of the
FlowSession interface. |
MockParameterMap |
A extension of parameter map that allows for mutation of parameters.
|
MockRequestContext |
Mock implementation of the
RequestContext interface to facilitate standalone flow artifact (e.g. |
MockRequestControlContext |
Mock implementation of the
RequestControlContext interface to facilitate standalone Flow and State unit
tests. |
TestFlowBuilderServicesFactory |
Factory that encapsulates configuration of default flow builder services for a test environment.
|
When you want to unit test one of your flows the
AbstractFlowExecutionTests
and its associated subclasses provide
a base you can extend.
When unit testing flow artifacts such as actions in isolation, the
MockRequestContext
is of particular interest.
All mock implementations provided by this package are NOT intended to be used for anything but standalone unit
tests. They are simple state holders, stub implementations, at least if you follow
Martin Fowler's reasoning. These classes
are called Mocks to be consistent with the naming convention in the rest of the Spring framework
(e.g. MockHttpServletRequest
, ...).