Timeline for Does simply running the code during development mean 'Testing'?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2016 at 8:45 | comment | added | Joe | @EthelEvans, I'd love to write unit tests, I've at least designed the UI using MVVM so that could be unit tested to a degree. But we simply don't have the resource/budget, I'm already struggling to persuade this guy the software is more complex than he thinks and explaining why features aren't done when 'they are easy, I can do that in excel'. | |
| May 6, 2016 at 10:16 | comment | added | Tom Bowen | I agree that this is the right answer, however @EthelEvans, I think you have it backwards, he's worried to say it's testing because "he said we didn't want to put any time into testing". Adding unit tests makes the situation worse for OP. | |
| May 5, 2016 at 21:08 | comment | added | Ethel Evans | This is the right answer. If you are using a more casual definition of testing from the person asking the question about testing, they will feel lied to. Technically, this "start it up and see if it works" testing is "manual testing", but I doubt it's what the asker means. In the meantime, make sure you document your conversation. Send a summarizing email to your boss or something, so he can't throw you under the bus later. Consider adding in some unit tests NOW. They are really hard to write in later and will change and improve your code design. #gratuitousAdvice | |
| May 5, 2016 at 19:22 | history | answered | user246 | CC BY-SA 3.0 |