You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@onami.apache.org by "Simone Tripodi (JIRA)" <ji...@apache.org> on 2013/02/03 22:02:13 UTC
[jira] [Commented] (ONAMI-75) Update tests from pure JUnit to use
Onami-Test to avoid boilerplate code
[ https://issues.apache.org/jira/browse/ONAMI-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569893#comment-13569893 ]
Simone Tripodi commented on ONAMI-75:
-------------------------------------
I already have that local modification in my local copy of the Onami repository, it is just a matter of committing it as soon as the onami-test artifact is available on the central repo
> Update tests from pure JUnit to use Onami-Test to avoid boilerplate code
> ------------------------------------------------------------------------
>
> Key: ONAMI-75
> URL: https://issues.apache.org/jira/browse/ONAMI-75
> Project: Apache Onami
> Issue Type: Bug
> Components: configuration, guava, scheduler, spi, validation
> Affects Versions: configuration-6.3.0, guava-0.2.0, scheduler-1.4.0, spi-1.0.0, validation-1.0.0
> Reporter: Simone Tripodi
> Assignee: Simone Tripodi
> Fix For: configuration-6.3.0, guava-0.2.0, scheduler-1.4.0, spi-1.0.0, validation-1.0.0
>
>
> Current tests in all components always define the list of modules that a Test class requires, create the injector and inject test members; this boilerplate and redundant code can be removed adopting the recently released onami-test.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira