Skip to content

Commit 2be0f32

Browse files
committed
Update When to use and Best practices in E2E tests section
1 parent 1849fe7 commit 2be0f32

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

recipes/automated-testing.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -191,12 +191,15 @@ lower level (integration or unit tests).
191191

192192
#### When to use
193193
- To validate user interactions and critical workflows in the application UI.
194-
- For testing full system integration across multiple services or components.
194+
- For testing specific user flows.
195+
- For making sure that critical application features are working as expected.
196+
- For better coverage of the most common user pathways.
195197

196198
#### When **not** to use
197199
- For data validation.
198200

199201
#### Best practices
202+
- Tests should be atomic and simple, all complicated tests should be thrown out.
200203
- Focus on the most important user workflows rather than attempting exhaustive
201204
coverage.
202205
- Each test should be able to run independently, with the environment reset to a

0 commit comments

Comments
 (0)