From cc601298675cf6d1d9745211cff77131da53dac8 Mon Sep 17 00:00:00 2001 From: 11Alone11 <90934356+11Alone11@users.noreply.github.com> Date: Sat, 3 Aug 2024 17:20:26 +0300 Subject: [PATCH] Fix layout testing.md --- src/guide/scaling-up/testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/guide/scaling-up/testing.md b/src/guide/scaling-up/testing.md index 0316d7a7e2..a2729abbd1 100644 --- a/src/guide/scaling-up/testing.md +++ b/src/guide/scaling-up/testing.md @@ -189,9 +189,9 @@ Component tests should focus on the component's public interfaces rather than in -- **DON'T** +**DON'T** - Don't assert the private state of a component instance or test the private methods of a component. Testing implementation details makes the tests brittle, as they are more likely to break and require updates when the implementation changes. +- Don't assert the private state of a component instance or test the private methods of a component. Testing implementation details makes the tests brittle, as they are more likely to break and require updates when the implementation changes. The component's ultimate job is rendering the correct DOM output, so tests focusing on the DOM output provide the same level of correctness assurance (if not more) while being more robust and resilient to change.