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

Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2014/04/16 10:28:14 UTC

[jira] [Assigned] (OPENEJB-2089) Provide ApplicationComposer feature as a JUnit @Rule

     [ https://issues.apache.org/jira/browse/OPENEJB-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau reassigned OPENEJB-2089:
-------------------------------------------

    Assignee: Romain Manni-Bucau

> Provide ApplicationComposer feature as a JUnit @Rule
> ----------------------------------------------------
>
>                 Key: OPENEJB-2089
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2089
>             Project: OpenEJB
>          Issue Type: Improvement
>          Components: tests
>            Reporter: Xavier Dury
>            Assignee: Romain Manni-Bucau
>         Attachments: OPENEJB-2089.patch
>
>
> Currently, ApplicationComposer uses the only one shot we have at specifying which Runner a JUnit test should use.
> This can easily be circumvented by exposing the same functionality through a JUnit @Rule (TestRule).
> By doing this, we could use ApplicationComposer with an other Runner (like Parameterized) and/or other @Rules.



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