SFINT-5832: Sort E2E tests migrate from Cypress to Playwright

[lvu285]

https://coveord.atlassian.net/browse/SFINT-5832

IN THIS PR:

• Added Playwright E2E tests for the quantic-sort component

UNIT TESTS:

• No need, as UTs already there

E2E PLAYWRIGHT TESTS:

• Playwright for Sort component

[github-actions]

Pull Request Report

PR Title

❌ Title should follow the conventional commit spec:
<type>(optional scope): <description>

Example: feat(headless): add result-list controller

Live demo links

• Storybook

• Playwright report

Bundle Size

File	Old (kb)	New (kb)	Change (%)
case-assist	242.9	242.9	0
commerce	354	354	0
search	414	414	0
insight	405.2	405.2	0
recommendation	255.1	255.1	0
ssr	407.4	407.4	0
ssr-commerce	371.3	371.3	0

SSR Progress

Use case	SSR (#)	CSR (#)	Progress (%)
search	39	44	89
recommendation	0	4	0
case-assist	0	6	0
insight	0	27	0
commerce	0	15	0

Detailed logs

search : buildInteractiveResult
search : buildInteractiveInstantResult
search : buildInteractiveRecentResult
search : buildInteractiveCitation
search : buildGeneratedAnswer
recommendation : missing SSR support
case-assist : missing SSR support
insight : missing SSR support
commerce : missing SSR support

[SimonMilord]

Suggested change

	import {SortObject} from './sortObject';
	import {SortObject} from './pageObject';

in line with my other comment

[SimonMilord]

should we test selecting with SPACE key here?
what about navigating with TAB or left/right arrow keys?

[lvu285]

I added test using Space to open Dropdown
Tab is not necessary as it wont trigger anything

[SimonMilord]

In line with my suggestion to test with space, you could probably modify this to take the key you want to use as argument (ENTER || SPACE)

[erocheleau]

Suggested change

	get sortPreviewHeader(): Locator {
	get sortPreviewButton(): Locator {

[mmitiche]

@erocheleau I will integrate the content from this PR: #4782 in this PR as well, to have more unit tests to test the component rather going E2E only.

[mmitiche]

The Insight Fixture should contain QuanticSortE2EFixtures + insightSteup and not QuanticSortE2ESearchFixtures + insightSetup

You can follow the following example:

ui-kit/packages/quantic/force-app/main/default/lwc/quanticTab/e2e/fixture.ts

Lines 15 to 27 in 7a21e86

	type QuanticTabE2EFixtures = {
	tab: TabObject;
	search: SearchObject;
	options: Partial<TabOptions>;
	};
	type QuanticTabE2ESearchFixtures = QuanticTabE2EFixtures & {
	urlHash: string;
	};
	type QuanticTabE2EInsightFixtures = QuanticTabE2EFixtures & {
	insightSetup: InsightSetupObject;
	};

.

[lvu285]

I will update this. Do you want I update pager too? as I followed your example on Pager component?

[mmitiche]

Need to be cleaned out according to the new unit tests that test the invalid sort options and custom sort sort options, no need for example for the invalidMessage selector.