re: The worst developers are those who complain there are no tests in a project VIEW POST


It's about degree and amount of test.

For example of web programming, my solution is unit test includes usecase and entity, not test controller and db. This will be more quick and reduce amount of tests.

If need , add a short time to do integration test for page and db.

More test for key point such as domain model.

No a simple line for test, just experience.


I do agree that testing everything is unnecessary. But some testing, especially on things that, when broken, disrupt the client's workflow or experience, is hugely important.


It's about confidence for remove bug quickly and project control. Test is a valuable tool in the age, unless you are a superman.

And the confidence that the bug is actually removed and will not come back.

code of conduct - report abuse