[
https://issues.apache.org/jira/browse/PLUTO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550080
]
Benjamin Gould commented on PLUTO-442:
--------------------------------------
There is a bug in the way that the test portlet determines whether or a not a
batch of tests fails or passes that cropped up when I added the extra portlet
lifecycle phases. Among other things, the
pluto-testsuite.afewfiltertests.patch patch solves this issue.
> 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: pluto-portal.patch,
> pluto-testsuite.afewfiltertests.patch, testsuite-annotations.diff,
> 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.
