How much time do you spent in unit testing? Do you even create unit tests for your software?
Martin Schumacher
7 replies
Replies
William Gump@xyz_333
Unit testing is a staple in my development process, Martin; I typically allocate about 30% of the development time to ensure robustness and future maintainability. Skipping it just seems to borrow time from the future, where debugging becomes far more costly.
Share
@xyz_333 30% is a great practice. I wish it was more of a standard, even 15-20 would do. The main problem and tests save me from is new version and hot fixes. How do you know that you didn't break anything without testing? It is not nice to have to say "I can work on X, but I have no idea what might break"
@xyz_333 I totally agree with 30%!
I think that skipping unit tests completely is not a good idea.
It is a powerful tool when used wisely.
On the other hand - I have experienced PMs forcing developers to write unit tests that didn't make much sense - just to "artificially" increase coverage. That doesn't make sense at all.
@xyz_333 @0xcaponte I totally agree. It may seem like that creating unit tests take too much time, but surely it's refunded later in the development process.
I dedicate a significant portion of my development cycle to unit testing, Martin; it's crucial for ensuring each component functions correctly before integration. Skipping unit tests is tempting for short-term gains, but investing the time upfront pays off in reliable, maintainable code.
Unit, integration and other tests are very important for us to provide a reliable software!
Ah, the time spent on unit testing varies depending on the complexity of the software and the project's requirements. Typically, I allocate a significant portion of my development time to writing unit tests because they're crucial for ensuring the reliability and robustness of the software. mold removal services /
Yes, I do create unit tests for my software. They're an integral part of my development process. Unit tests help catch bugs early, validate the correctness of individual components, and provide a safety net for refactoring or making changes to the codebase. So, yeah, I definitely make sure to include them in my workflow.