ReportScreen Reassure test Flakiness

[mountiny]

Problem

As we roll out more Reassure based performance test, we are facing some flakiness in their outpust where they provide false positives. More context here https://expensify.slack.com/archives/C03UK30EA1Z/p1699546341608409?thread_ts=1699521471.426869&cid=C03UK30EA1Z

This is a problem as flakiness in these tests undermines its entire purpose, its not clear as of now what exactly is the root cause of the flaky tests here.

Solution

Identify the root cause of the flakiness and update the reassure test suite to get rid it of, since we measure the count of re-renders, this should not be happening with reassure so most likely this is an error on our side

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[mountiny]

cc @adhorodyski

[mountiny]

Tests have been skipped in this PR #31131 so we can resolve the root cause next week

[mountiny]

@adhorodyski @OlimpiaZurek How is it looking with this one, do you have any ETA for fix?

[OlimpiaZurek]

Hey @mountiny I'll look into it today. We don't have a specific ETA for this as we need to find the root cause first.