A mistake less experienced software engineers make when it comes to estimations: They break out maintainability/quality. Eg “building the feature is 2 weeks, adding automated tests another 3 days”. What follows by less technical stakeholders is a push to remove the latter.
61
186
2,109
551,808
You don’t build the project, then add automated tests, you add automated tests then build, it’s called TDD
6
14
11,412
Some do and we are talking unit tests with TDD. I’ll admit I think TDD is ok but I fund it too rigorous to use all time. Wrote automated tests as there’s a lot more that can make sense. Eg integration tests, E2E tests, load tests, perf tests etc could be part of maintainability
4
37
9,968
Replying to @GergelyOrosz @SamProgramiz
For most applications, you also get a bigger bang for your buck writing integration and acceptance tests than unit tests. It's also common to forget that even tests themselves introduce a maintenance cost like any other code. See attached meme

Feb 26, 2023 · 9:06 PM UTC

1
2
8
1,189
Sort replies: Relevant Recent Liked
Replying to @j_ckao @SamProgramiz
This greatly depends on the stack as well, ease/stability of integration tests. Eg in web dev integration tests are easier and more useful. For backend, depends on your env
1
668