| ▲ | simonw 5 hours ago | |||||||
I don't see testing as a quality thing any more, I see it as a developer productivity thing. If my project has tests I can work so much faster on it, because I can confidently add tests and refactor and know that I didn't break existing functionality. You gotta pay that initial cost to to get the framework in place though. That takes early discipline. | ||||||||
| ▲ | GrumpyYoungMan 2 hours ago | parent | next [-] | |||||||
Developer testing is checking whether the code does what the developer themself thinks it should. QA testing is checking whether the code does what the customers / users / rest of the world thinks it should. | ||||||||
| ▲ | smackeyacky 3 hours ago | parent | prev [-] | |||||||
It’s a lot faster and easier than it used to be. Things like xUnit in the .net world make setting up tests friction free to the point where I question a codebase that doesn’t have some kind of basic unit tests. It doesn’t make mock testing or integration testing easier but I would argue if you know the base code and logic is sound those tests are less relevant. One thing I found is that if testing is easy, your code structure does change a bit to aid with a “test first” approach and I don’t hate it. I thought it made me slower but it doesn’t, it ensures that when all the ground work is finished, the gnarly part of wiring everything up goes much faster. | ||||||||
| ||||||||