Timeline for Time difference between developing with unit tests vs no tests
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2016 at 17:20 | comment | added | enderland | Writing tests is still trivial in VBA. Having all the fancy features that some unittest frameworks have? That's harder, but running a program called mainTest() that calls all your test modules isn't really that hard. | |
| Jun 17, 2016 at 10:02 | comment | added | RubberDuck | All fair points @ArthurHavlicek. | |
| Jun 17, 2016 at 6:25 | comment | added | Diane M | There is a few reasons I won't use this because it doen't fit my needs (I'm on few days tasks at most, locked environment, successor won't bother 3rd parties). Good comment though, language is not an excuse in itself :) | |
| Jun 16, 2016 at 23:23 | comment | added | RubberDuck | "Should I really develop a test module for VBA?" Damn right you should. rubberduckvba.com/Features#unitTesting | |
| Jun 16, 2016 at 13:34 | history | edited | Diane M | CC BY-SA 3.0 | added 120 characters in body |
| Jun 16, 2016 at 11:51 | history | answered | Diane M | CC BY-SA 3.0 |