Timeline for Unit testing newbie team needs to unit test
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 30, 2018 at 14:07 | comment | added | Todd | You second para is spot on. The code is hard to test but because its on a legacy code-base with no tests, refactor is not an option. The test then can be so difficult to implement that it turns off people to even bother. | |
| Dec 14, 2011 at 1:04 | history | edited | azheglov | CC BY-SA 3.0 | added 175 characters in body |
| Oct 11, 2010 at 4:31 | comment | added | Sergio Acosta | I think this is a great way: Show the team first how end-to-end tests can be automated and run on every build. They don't even need to write the tests, you can do that all by yourself if the team is hard to convince. As soon as they see how great is to have automated feedback each time they change something, they will be the ones asking you how to do more of that stuff. | |
| Oct 11, 2010 at 1:56 | history | answered | azheglov | CC BY-SA 2.5 |