Currently the tests for the Select component is not consistent and it results in a slowed developer experience as tests fail on the PR and have to be re-run multiple times to get into a succeeded state.
This is for the tests that have screenshot comparisons the following has been observed
The Select component tests are flaky in some cases fails due to 1px difference (In some cases re-running the tests results in a eventual pass).
Async rendering tests are not in the correct state when the actual screenshot is taken this results in discrepencies when comparing the 'Expected' vs 'Actual' screenshots (Look into waiting for the selector).
This will have a knock on effect on other branches PRs if they merge the changes from a branch that has changes to the Select component or its tests.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Components Version
0.9.1
Which package type are you using?
Unbundled
What type of bug is this?
Behaviour Error
Test Case/Reproduction
No response
Description
Currently the tests for the Select component is not consistent and it results in a slowed developer experience as tests fail on the PR and have to be re-run multiple times to get into a succeeded state.
This is for the tests that have screenshot comparisons the following has been observed
Code of Conduct