Add information in the sidebar to indicate that element target and variants are mandatory

• Type: Story
• Status: Ready for QA
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: AB Testing
• Labels:
  • fc_19_12
• Epic Link: tango-ab-testing-intuitive-variants
• Sprint: TANGO | SP_25 | Nov27-Dec11
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/81508

Motivation

Providing more clear information in the sidebar about what fields are mandatory to help the user run the test correctly.

Acceptance Criteria

AB Test created with Click goal:

• Given an experience
• When the user creates an AB Test with Click goal for this experience
• Then the click goal section appears as mandatory

AB Test requires minimum one Variant to test against Control:

• Given an experience
• When the user creates an AB Test for this experience
• Then the variants sections appears as mandatory

Design

https://www.figma.com/file/GtTiZV12ZZJJ4YQ6Jv2GJD/LPS-103750-warn-no-element-set-click-goal?node-id=1%3A1358

Test Scenarios 

AC ID	Test Strategy	Test Scenarios	Is it covered by FrontEnd? (JS-Unit)	Is it covered by BackEnd? (unit or integration)
01	Smoke	Validate if, in the AB Test, the sidebar informs the user that the click goal section to select the element target is mandatory	YES	N/A
01	Sanity	Validate if, in the AB Test, if the user tries to run some test without set the click goal target an error appear	YES	YES
02	Smoke	Validate if, in the AB Test, the sidebar informs the user that minimum one variant is mandatory to test against Control	NO	N/A
02	Sanity	Validate if, in the AB Test, the sidebar informs the user that minimum one variant is mandatory to test against Control if the user add variants and remove all variants	NO	N/A
02	Sanity	Validate if, in the AB Test, if the user tries to run some test without creating at least one variant an error appear	YES	YES

Frontend:

✓ Sidebar indicates mandatory sections in sidebar with asterisks icons (20ms)
✓ Error messages appears when the user clicks in review and run and there is no click target element selected (22ms)
✓ Error messages appears when the user clicks in review and run and there is only the control variant created (21ms)

Backend:

com.liferay.segments.service.test.SegmentsExperimentLocalServiceTest#testRunSegmentsExperimentWithClickGoalAndEmptyTarget
com.liferay.segments.service.test.SegmentsExperimentLocalServiceTest#testRunSegmentsExperimentWithControlVariant
**