[PLUTO-729] TCK: Contesting usage of upper-case portlet modes and window states in Portlet Hub tests

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0, 3.0.1
• Fix Version/s: 3.0.2-TCK
• Component/s: tck
• Assignee: Neil Griffin (Inactive)
• Reporter: Neil Griffin (Inactive)
• Created: 22/Aug/18 13:22
• Updated: 14/Dec/22 14:37
• Resolved: 10/Apr/19 19:15

Description

This issue challenges the usage of upper case portlet modes and window states in Portlet Hub tests.

The JSDoc for the Portlet Hub setPortletMode function states:

The strings defined by the

Unknown macro: {@link PortletConstants}

object should be used to specify the portlet mode.

In addition, the JSDoc for the Portlet Hub setWindowState function states:

The strings defined by the

Unknown macro: {@link PortletConstants}

object should be used to specify the window state.

The portlet constants are defined in the JSDoc with lower case values:

portlet.js

 * @property   {string}       VIEW        Specifies portlet mode 'view'    
 * @property   {string}       EDIT        Specifies portlet mode 'edit'    
 * @property   {string}       HELP        Specifies portlet mode 'help'    
 * @property   {string}       NORMAL      Specifies window state 'normal'
 * @property   {string}       MINIMIZED   Specifies window state 'minimized'
 * @property   {string}       MAXIMIZED   Specifies window state 'maximized'

However, certain Portlet Hub related TCK tests are using an upper case value. For example, V3PortletHubTests_SPEC_23_JSState_clone3 has:

state.setPortletMode('VIEW');
state.setWindowState('NORMAL');