-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
Just came across this very interesting article about testing challenges in the interactive programming game Factorio. There the author lays out reasons for why having tests depend on each other makes refactorings easier.
Test A -> tests feature A
Test B -> tests feature B
# No need to run this test if "Test A" or "Test B" fails
Test C -> tests how feature A + B work togetherThe idea is that one usually has e2e test which are a bit more low level, like test feature A and others which usually exercise multiple features at once and how they work togther. So in that situation it's not useful to run tests which depend on A to work, when A is broken. It's totally fine to just run the tests for A and skip all further tests that depend on feature A to work.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels