> I took it as: if you only have E2E tests then retrofitting unit tests is hard.
That's been my experience. My point is that the reason the project has E2E tests and not unit tests is because it was easier to add E2E tests.
That's been my experience. My point is that the reason the project has E2E tests and not unit tests is because it was easier to add E2E tests.
My experience agrees with this. Adding unit tests to untestable code (think: class has 10 dependencies that it news up being the first branching of a depdendecy graph to be untangled) requires refactors that just don’t get done with the busyness of other priorities.