Analyze and group open flaky tests ticket

[chloeYue]

What is this about?

We have identified a significant number of flaky tests in our test suite that are causing instability and unreliable test results. This ticket aims to analyze the open flaky tests, categorize them based on their root causes, and propose actionable steps to address them.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response

[chloeYue]

Data on 27 Sep.

Extension Platform: (25 tickets)
#27131
#26009
#26368
#26418
#26501
#26611
#26614
#27390
#27128
#26638
#27336
#26502
#26899
#27419
#27422
#24651
#21494
#22567
#22568
#22713
#24655
#24657
#24658
#24668
#24669

Confirmation: (4 tickets)
#24633
#19823
#19824
#22563

Swaps: (3 tickets)
#24640
#24667
#26311

Snaps: (3 tickets)
#26579
#26804
#27276

Accounts: (1 tickets)
#24653

Assets: (3 tickets)
#24637
#26759
#27133

Wallet UX: (1 ticket)
#27455

[chloeYue]

Close this ticket because all flaky tests tickets assigned to extension platform team are added to the NEXT section on our planning board, and categorised under O1KR3