You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Lance (JIRA)" <ji...@apache.org> on 2014/03/19 12:12:42 UTC

[jira] [Commented] (TAP5-2273) TapestryIOCJunit4ClassRunner

    [ https://issues.apache.org/jira/browse/TAP5-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940395#comment-13940395 ] 

Lance commented on TAP5-2273:
-----------------------------

Something to consider is whether the registry is created once per test class or before each test method

See spring's @DirtiesContext and DirtiesContext.ClassMode
- http://docs.spring.io/spring/docs/3.0.x/api/org/springframework/test/annotation/DirtiesContext.ClassMode.html
- http://docs.spring.io/spring/docs/3.0.x/api/org/springframework/test/annotation/DirtiesContext.html

Could be verified with a mutable service and junit's @FixMethodOrder (http://www.javacodegeeks.com/2013/01/junit-test-method-ordering.html)

> TapestryIOCJunit4ClassRunner
> ----------------------------
>
>                 Key: TAP5-2273
>                 URL: https://issues.apache.org/jira/browse/TAP5-2273
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-test
>            Reporter: Lance
>            Priority: Minor
>
> Implement a TapestryIOCJunit4ClassRunner in a similar style to SpringJUnit4ClassRunner (http://docs.spring.io/spring/docs/2.5.6/api/org/springframework/test/context/junit4/SpringJUnit4ClassRunner.html)



--
This message was sent by Atlassian JIRA
(v6.2#6252)