As a user I can easily select a click goal target

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Pages > A/B Testing for Content Pages
• Labels:
  • fc_19_11
  • fc_19_12
• Epic/Theme:
  • AB_Testing
• Epic Link: tango-ab-testing-enhanced-click-selection
• Sprint: TANGO | SP_23 | Oct30-Nov13, TANGO | SP_24 | Nov13-Nov27, TANGO | SP_25 | Nov27-Dec11, TANGO | SP_26 | Dec12-Jan03

Motivation

According to the data obtained by Usability Tests, users find it confusing:

• to set an element as the click target goal which may cause not being able to start the test.
• that after clicking the button to set the element, it is changed to disable and the not allowed cursor shows up.
• to know the reason why it is not possible to run the test when there is not a clickable element set.

Design

Review and Run button should not be disabled to validate if all configurations needed are set and provide the user with valuable information that unlock their path.

https://www.figma.com/file/GtTiZV12ZZJJ4YQ6Jv2GJD/LPS-103750-warn-no-element-set-click-goal?node-id=2%3A0
https://www.figma.com/file/SmoizlGVwb4KH3ywzHf0m0/LPS-103746-highlight-clickable-elements-click-goal?node-id=1%3A7159

Aceptance Criteria

1. No click goal

• Given an AB test with click goal
• When there is not an element set and when the run test is clicked
• Then a warning alert appears to inform the user why it is not possible to run the test yet

2. Set element has been deleted

• Given an AB test with click goal
• When the element set as click element is deleted
• Then a warning alert shows to inform the users that they need to select another element as click target.

3. Button states

• Given an AB test with click goal
• When clicking to Set Element
• Then the button turn to active (not disabled)
• When clicking again
• Then the button turn to default again

4. Cursor behavior

• Given an AB test with click goal
• When clicking to Set Element
• Then the non selectable Elements on page have the pointer not allowed

5. Style adjustments to highlight selectable elements

• Given an AB test with click goal
• When clicking Set Element
• Then the selectable elements in the interface are highlighted with a more evident box

Test Scenarios

AC ID	Test Strategy	Test Scenarios	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd ? (unit or integration)
02	Sanity	Validate if in the AB Test, when the user delete the clickable element that was setted, the warning alert appears	NO	N/A
03	Regression	Validate if in the AB Test, when the user clicks in the Set Element, this button turns from default mode to active mode	YES	N/A
03	Smoke	Validate if in the AB Test, when the user clicks in the Set Element, two times, this button turns from default mode to active mode and turn back to the default mode	YES	N/A
04	Smoke	Validate if in the AB Test, when the user clicks in the Set Element, all elements in the page, that is not clickable, have the pointer not allowed	NO	N/A
05	Regression	Validate if in the AB Test, when the user clicks in the Set Element, all elements in the page, that is not clickable, change the opacity(the 5th Acceptance Criteria was updated)	-	-
05	Sanity	Validate if in the AB Test, when the user clicks in the Set Element, all elements in the page, that is clickable, are highlighted	NO	N/A
06	Integration	Validate if in the AB Test, when the user tries to run the experiment without goal target, it's not possible	NO	YES

Frontend tests:

✓ Experiment renders when goal value is click (110ms)
✓ User clicks in set element button, the button turns from default to active mode (31ms)
✓ The user can set a click target element in a draft experiment (4ms)
✓ The user can edit a selected click target element in a draft experiment (4ms)
✓ When the user set element as click target, then the element is set as the click target and the id of the element as a link (4ms)

Backend tests:
✓ com.liferay.segments.service.test.SegmentsExperimentLocalServiceTest#testRunSegmentsExperimentWithClickGoalAndEmptyTarget