feat(quantic): QuanticResultsPerPage fixes and refactor tests

[erocheleau]

SFINT-5851

IN THIS PR:

• We are migrating E2E tests for the quanticResultsPerPage component from Cypress to Playwright and adding unit tests.
• We are also updating the behavior whenever an erroneous initialChoice or no initialChoice is passed to the component. We said

"The initial selection for the number of result per page. This should be part of the choicesDisplayed option. By default, this is set to the first value in choicesDisplayed."

But in reality, we were always defaulting to the value 10 whenever no value was passed,
And if the value was not within the choicesDisplayed we would completely crash Quantic initialization by throwing an error.

Instead now, if the value is invalid (such as not a number, missing or not part of the choicesDisplayed) we actually default to the first value in choicesDisplayed. Log an error in the console, but do not throw.

If the values in choicesDisplayed is invalid, we log an error in the console, and display the componentError, but no longer throw an error.

UNIT TESTS:

E2E TESTS:

[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	243.9	243.9	0
commerce	355.2	355.2	0
search	415.1	415.1	0
insight	406.3	406.3	0
recommendation	256.2	256.2	0
ssr	409	409	0
ssr-commerce	373	373	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

[mmitiche]

@erocheleau to avoid issues with the versioning we should update the PR title to test(quantic): .... or fix(quantic): .... as this PR also fixes the behaviour of the component.

[erocheleau]

@erocheleau to avoid issues with the versioning we should update the PR title to test(quantic): .... or fix(quantic): .... as this PR also fixes the behaviour of the component.

Very true, I forgot! thanks!

[SimonMilord]

After addressing mehdi's concerns and comments, it seems good to me!

[mmitiche]

Looking good, GG!