[PLUTO-652] TCK: V2RequestTests getPortalContext test failures caused by an incorrect version in the context-path

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: tck
• Assignee: Neil Griffin (Inactive)
• Reporter: Neil Griffin (Inactive)
• Created: 28/Dec/16 16:40
• Updated: 28/Dec/16 16:51
• Resolved: 28/Dec/16 16:51

Description

The following test cases assume a hard-coded version of "2.1.0-SNAPSHOT" in the context-path:

• V2RequestTests_PortletRequest_ApiResource_getPortalContext
• V2RequestTests_PortletRequest_ApiRender_getPortalContext
• V2RequestTests_PortletRequest_ApiEvent_getPortalContext
• V2RequestTests_PortletRequest_ApiAction_getPortalContext

For example:

RequestTests_PortletRequest_ApiResource.java

if(gpc.equals("pluto-portal-driver/2.1.0-SNAPSHOT")) {
    tr36.setTcSuccess(true);
} else {
    tr36.setTcDetail("The PortalContext for the portal is invalid");
}

This issue needs a more comprehensive fix as part of PLUTO-653, but can be fixed in the short term with the following:

-      if(gpc.equals("pluto-portal-driver/2.1.0-SNAPSHOT")) {
+      if(gpc.startsWith("pluto-portal-driver/3.0")) {

Issue Links

• is related to: PLUTO-653 TCK: V2RequestTests getPortalContext test cases only work for Apache Pluto