[
https://issues.apache.org/jira/browse/OPENEJB-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545354#comment-13545354
]
Jakub Marchwicki commented on OPENEJB-1981:
-------------------------------------------
The attached patch includes the following:
* Configuration validation code moved to a separate, static validator class
* Introducing TestRunner which is testing framework independent.
* The original ApplicationComposer class is using the runner instance in a
jUnit fashion
* New org.apache.openejb.testing.testng.ApplicationComposer class in added to
adapt to the TestNG environment
* Additional application-composer-testng example has been added
The changes can be lookup here:
https://github.com/kubamarchwicki/openejb/compare/trunk...testng as well
What hasn't been done:
* The original org.apache.openejb.junit.* package hasn't been touched. The
configuration annotations (@Module, @Configuration, etc) are left there though
the org.apache.openejb.testing seem a more suitable place for those. I didn't
want to introduce a change that is pervasive through too many components.
> Add ApplicationComposer inspired class to run TestNG tests
> ----------------------------------------------------------
>
> Key: OPENEJB-1981
> URL: https://issues.apache.org/jira/browse/OPENEJB-1981
> Project: OpenEJB
> Issue Type: New Feature
> Components: general
> Affects Versions: 4.5.1
> Reporter: Jakub Marchwicki
> Priority: Trivial
> Attachments: application-composer-testng.patch
>
>
> Story
> *In order* to write and run my intergration tests in my TestNG environment
> *As a* developer
> *I want* support for TestNG inspired by the ApplicationComposer jUnit runner.
> Rationale:
> ApplicationComposer is purely jUnit based solution. The test validation and
> container bootstrapping code can be abstracted (made independent of the test
> framework) so that two adapters can be introduced: jUnit and TestNG.
--
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
