From c25e3c85575d61cae0c285c8ff26e3def18a769e Mon Sep 17 00:00:00 2001 From: Github Date: Wed, 30 Oct 2024 17:37:21 +0100 Subject: [PATCH] cr fix --- contributingGuides/REASSURE_PERFORMANCE_TEST.md | 1 - 1 file changed, 1 deletion(-) diff --git a/contributingGuides/REASSURE_PERFORMANCE_TEST.md b/contributingGuides/REASSURE_PERFORMANCE_TEST.md index e4fc73b0b9ae..0de450b78875 100644 --- a/contributingGuides/REASSURE_PERFORMANCE_TEST.md +++ b/contributingGuides/REASSURE_PERFORMANCE_TEST.md @@ -10,7 +10,6 @@ We use Reassure for monitoring performance regression. It helps us check if our ## Performance Testing Strategy (`measureRenders`) - Before adding new tests, check if the proposed scenario or component is already covered in existing tests. Duplicate tests can slow down the CI suite, making it harder to spot meaningful regressions. -- Review the current test suite to ensure your test scenario or component isn’t already being tested elsewhere. - Test only scenarios that cover new or unique interactions. Avoid testing repetitive user actions that could be captured within a single, comprehensive scenario. - Where applicable, use utility functions and helper methods to consolidate common actions (e.g., data mocking, scenario setup) across tests. This reduces redundancy and allows tests to be more focused and reusable. - The primary focus is on testing business cases rather than small, reusable parts that typically don't introduce regressions, although some tests in that area are still necessary.