Timeline for Should I be unit testing during prototyping/preparing for beta?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2018 at 13:42 | vote | accept | Chris Cirefice | ||
| Sep 9, 2018 at 16:51 | comment | added | Chris Cirefice | and as more features are added, write tests when I build them. Basically I've just been pumping out code as fast as possible to get this product into peoples' hands. My client (the consultant) will save approximately 30 hours per month simply from the elimination of manual tasks. Considering she bills at $125/hour, it's also valuable for her clients (the people who will also use the software). So it's been a rush to get things off the ground. I've done manual testing and that has worked so far, but I do plan on writing tests in the future. Just maybe not TDD, since I have no experience. | |
| Sep 9, 2018 at 16:49 | comment | added | Chris Cirefice | Thanks for your answer. When I say "prototype", I really mean software that will be put into production. It won't be throwaway code. That aside, I've sadly never done TDD... and even worse, I work alone (on a freelance basis), so I have nobody to mentor me! I've told my client that I haven't spent any time writing tests for the software yet, but that it *will * be important as soon as we get into beta. At that point, the rapid development will stop as people test the features over the course of months. The plan is to start writing tests for the existing code during that period... 1/2 | |
| Sep 9, 2018 at 16:08 | comment | added | candied_orange | No no no. "velocity would be higher if you were doing TDD, even under changing requirements." is wrong. That should read: "especially under changing requirements." ;) | |
| Sep 9, 2018 at 1:44 | history | edited | l0b0 | CC BY-SA 4.0 |
added 223 characters in body
|
| Sep 9, 2018 at 1:37 | history | answered | l0b0 | CC BY-SA 4.0 |