Comments by "Ton Bong" (@tongobong1) on "Testing Is Bad For Developer Productivity" video.

I would love to see a video about when to delete unit tests that are no longer needed because we have more useful unit tests that test more code.
4
Writing tests is EASY once you STOP COMPLICATING about writing tests. Just write some simple straightforward tests and you are good to go and forget about writing tests for every edge condition that can occur.
4
You don't understand the agile process. Agile means that you don't know exactly what a customer wants so you create a small upgrade and show it to customer and he will give you more input so you can change it until the customer is satisfied with the result. Only then you can create a test that will preserve the functionality after many small changes of the code in the future cycles. The main benefit of writing tests is to protect the current functionality from future upgrades.
3
Yes Dave is lost in the theory that is far from reality.
1
But there are many terrible unit tests in the world. All the London style tests should be deleted because they are worse than having no tests.
1
@rfphill yes those tests that mock everything outside the class under tests are the London style unit tests.
1
Yes but you would be surprised to know how much of advice on writing good unit tests is just terribly wrong and also the best parts are completely missing from most books... For example how to determine which tests to delete when we cover the code with better/more useful unit tests...
1
@orlovskyconsulting no don't delete the code just the tests that duplicate testing that code. Keep the most useful tests that are a bit larger and delete small tests that are already covered by larger teste. It is better to have 10 large unit tests - that are stil unit tests and not integration tests than having 100 small unit tests.
1
@orlovskyconsulting crazy that youtube censored my answer to you. I hope you will get this answer: You should just delete the tests that are testing the code more than one time and don't delete the code. It is better to have 10 large unit tests than 100 small unit tests that test the same code.
1
@HakanaiVR but we sometimes want to fail at the edge conditions. For example conditions that should never occur in the production software. We want to get the exception so to know there is something seriously wrong. We don't want to hide the failure.
1
@HakanaiVR This is not the edge condition that you described. You described the change in functionality. When change happens and old unit tests that covered the old functionality fail we should delete them. It is naive to think anyone can write the application correctly from the start. I guess you don't have much of experience writing code.
1