A common antipattern is to test a lot of behavior together over and over. This results in duplication across tests, low signal to noise ratio, more maintenance effort, longer runtimes. Worst case scenario, overreliance on expensive end-to-end tests for various edge cases. For instance filling out the same form again and again with different inputs. The solution is to write tests broken down into composable units. You will have to test that a few combinations work together but not exhaustively. Another plus for writing composable tests is that it helps enforce composability of the source code.
Hmm feel like im missing something on this one
A common antipattern is to test a lot of behavior together over and over. This results in duplication across tests, low signal to noise ratio, more maintenance effort, longer runtimes. Worst case scenario, overreliance on expensive end-to-end tests for various edge cases. For instance filling out the same form again and again with different inputs. The solution is to write tests broken down into composable units. You will have to test that a few combinations work together but not exhaustively. Another plus for writing composable tests is that it helps enforce composability of the source code.
did this get cut too early?