[
https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Gould updated PLUTO-442:
---------------------------------
Attachment: testsuite-with-phase-annotations.patch
This patch updates the test suite so that JSR 286 test may more easily be
written against the testing framework. This patch adds the following features:
1) Each portlet test can implement a doHeaders() function (default does
nothing) that gets called by TestPortlet.doHeaders()
2) Annotations have been added to define the portlet lifecycle phase in which
each test method should run. If a class is not annotated, the default phase is
Render. The @DefaultTestPhase annotation causes all test methods on a
PortletTest implementation to be run in the given phase, unless an individual
method is annotated with @TestPhase, in which case the default is overriden.
3) Test methods can now have signatures that have specific sub-interfaces of
PortletRequest (before, all test methods could only have arguments containing
PortletRequest or PortletResponse, rather than RenderRequest, ActionRequest,
etc.) Obviously, the test method signature must agree with the phase denoted
by its annotation(s). For backwards compatibility, test methods can still have
signatures containing PortletRequest or PortletResponse.
4) Updated all interfaces and implementations with generics and removed
compiler warning related to Java 5 language features.
> Create a Testsuite for JSR-286 features
> ---------------------------------------
>
> Key: PLUTO-442
> URL: https://issues.apache.org/jira/browse/PLUTO-442
> Project: Pluto
> Issue Type: Improvement
> Components: portlets-testsuite
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Craig Doremus
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: testsuite-with-phase-annotations.patch
>
>
> We need to add JSR-286 (Portlet 2.0) tests to the testsuite. It might be best
> to create separate portlets for these tests since JSR-286 adds features that
> facilitate interportlet communication (eventing and public render parameters).
> This issue is a parent issue with specific tasks linked below it including
> PLUTO-366, PLUTO-367 and PLUTO-368 .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
