Skip to content

Commit 1a149df

Browse files
authored
Update readme.md
1 parent 0afd174 commit 1a149df

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

readme.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Guidelines for CI in the JS world (9 bullets)
6363

6464
<br/>
6565

66-
## ⚪️ 0. The Golden Rule: Design for lean testing
66+
## ⚪️ 0 The Golden Rule: Design for lean testing
6767

6868
:white_check_mark: **Do:**
6969
Testing code is not like production-code - design it to be dead-simple, short, abstraction-free, flat, delightful to work with, lean. One should look at a test and get the intent instantly.
@@ -895,7 +895,7 @@ it("When updating site name, get successful confirmation", async () => {
895895

896896
# Section 3️⃣: Frontend Testing
897897

898-
## ⚪ ️ 3.1. Separate UI from functionality
898+
## ⚪ ️ 3.1 Separate UI from functionality
899899

900900
:white_check_mark: **Do:** When focusing on testing component logic, UI details become a noise that should be extracted, so your tests can focus on pure data. Practically, extract the desired data from the markup in an abstract way that is not too coupled to the graphic implementation, assert only on pure data (vs HTML/CSS graphic details) and disable animations that slow down. You might get tempted to avoid rendering and test only the back part of the UI (e.g. services, actions, store) but this will result in fictional tests that don't resemble the reality and won't reveal cases where the right data doesn't even arrive in the UI
901901

@@ -1166,7 +1166,7 @@ test('movie title appears', async () => {
11661166

11671167
<br/>
11681168

1169-
## ⚪ ️ 3.5. Watch how the content is served over the network
1169+
## ⚪ ️ 3.5 Watch how the content is served over the network
11701170

11711171
![](https://img.shields.io/badge/🔧%20Example%20using%20Google%20LightHouse-blue.svg
11721172
"Examples with Lighthouse")

0 commit comments

Comments
 (0)