[
https://issues.apache.org/jira/browse/TAP5-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-918:
--------------------------------
This issue has been last updated about 1.5 years ago and has no information
about the versions that are affected. That makes it hard to determine whether
it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most
recent development preview of Tapestry (5.4-beta-6), both of which are
available from Maven Central, please update it as soon as possible, adding the
respective version(s) to the issue's "Affects Version/s".
> Add mocks to registry with lifecycle for testing
> ------------------------------------------------
>
> Key: TAP5-918
> URL: https://issues.apache.org/jira/browse/TAP5-918
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Reporter: Adriaan Joubert
>
> For tests that use the IoC registry it would be nice to be able to override
> an existing binding so that the registry will return a Mock object from a
> test.
> This also requires a lifecycle that can deal with objects being recreated for
> successive tests for both singleton and per-thread services. This will
> presumably require overriding the scope on an existing service binding.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
