[
http://issues.ops4j.org/browse/PAXWICKET-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836#action_13836
]
Andreas Pieber commented on PAXWICKET-79:
-----------------------------------------
This issue should also be used to add an Testing page to
http://wiki.ops4j.org/display/paxwicket/Developer+Guide explaining how
integration tests are mend to be for pax-wicket
> Create one integration test project instead of using three
> ----------------------------------------------------------
>
> Key: PAXWICKET-79
> URL: http://issues.ops4j.org/browse/PAXWICKET-79
> Project: Pax Wicket
> Issue Type: Improvement
> Components: tests
> Reporter: Andreas Pieber
> Fix For: 1.0.0.M1, 1.0.0.RELEASE
>
>
> Currently we're using three integration tests problems (bootstrap,
> classResolverTest, lifecycleTest). Instead it would be sufficient to pack
> them all into one itest project. This would help on one hand to minimize the
> different projects new devs have to "learn" and on the other hand would
> remove the nasty work around done to include bootstrap into classResolverTest
> and lifecycleTest.
> BTW, this issue requires to fix PAXWICKET-78 first, because in this case we
> can remove the bundle-projects and condense the code of the three testing
> projects into one root project
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
