As a Marketer, I can select "input type = Submit" elements as a click target

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.4.13 DXP GA1, Master
• Component/s: Pages > A/B Testing for Content Pages
• Labels:
  • d_20_09
  • d_20_12
  • fc_21_01
• Epic/Theme:
  • AB_Testing
• Epic Link: tango-ABTesting-extend-clickable-elements
• Sprint: TANGO | #44 DIS | Aug28-Sep11, TANGO | #49 DIS | Nov13-Nov27, TANGO | #50 DIS | Nov27-Dec11, TANGO | #51 DEV | Dec11-Dec28, TANGO | #52 DEV | Jan12-Jan22, TANGO | #53 DEV | Jan22-Feb05
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/688

Motivation

When the A/B testing feature was delivered, only buttons and links could be set as clickable elements. As one of the most used marketing resources are forms, we will need to include the Input elements as clickable elements too.

Design

N/A

Technical Requirements

• When the user selects “Click” as the goal of an A/B test, not only buttons and links but also Inputs (<input type="submit" id="customId" />) are highlighted and can be selected as click goals

Acceptance Criteria

• Given a page and the AB testing panel with a created AB testing
• When the user clicks on the Select element button
• Then all the <input type="submit"/> elements on the page are highlighted and can be selected, and when selected, the ID of the selected element shows in the ID box

–

• Given a page and the AB testing panel with a created AB testing
• When the user enters the ID of an <input type="submit" id="customId" /> element in the ID Element box and hits enter
• Then all the <input type="submit"/> elements get highlighted and the <input type="submit" id="customId" /> element is selected

–

• Given a page and the AB testing panel with a created AB testing
• When there's an <input type="submit"/> with no ID 
• Then the matching element doesn't show as selectable 

–

• Given a click goal test on an <input type="submit" id="customId" /> element
• When the ID accomplishes with the conditions (is unique in the page, and the same for all page's variants, Does not change across requests, Does not change across published-draft status and Does not change across staging-live status)
• Then the element will be rightly measured in AC

–

 h1. Test Scenarios

AC ID	Test Strategy	Test Scenarios	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd? (unit or integration)	Poshi?
01	Low	When the user clicks on the Select element button, all the <input type="submit" id="customId" /> elements on the page are highlighted and can be selected, and when selected, the ID of the selected element shows in the ID box	NO	NO
02	Medium	When the user enters the ID of an <input type="submit" id="customId" /> element in the ID Element box and hits enter, the matching element gets highlighted and selected	NO	NO
03	Medium	When there's an <input type="submit" id="customId" /> with no ID, the matching element doesn't show as selectable	NO	NO
04	Low	When there's an <input type="submit" id="customId" /> with an ID, the matching element is shown as selectable	NO	NO
05	High	When the ID of an <input type="submit" id="customId" /> element accomplishes all the conditions (is unique in the page, and the same for all page's variants, Does not change across requests, Does not change across published-draft status and Does not change across staging-live status), the element will be rightly measured in AC	NO	NO

NOTE: The rest of the scenarios involving other clickable elements will be tested in LPS-119475