Testing is always time consuming, but in many cases, testing time can be reduced through automation. How are you doing it? Take the poll and let us know, and please tell us how you handle testing and test automation below in the Comments section!
Testing is always time consuming, but in many cases, testing time can be reduced through automation. How are you doing it? Take the poll and let us know, and please tell us how you handle testing and test automation below in the Comments section!
That's an interesting take Doug.
By "in production" do you mean a product that's about to be released to production manufacturing, or a product actually deployed in production which you automate health checking for to ensure it's working properly?
Test automation in R&D and development is absolutely and always worth the effort - we would live and die by the quality of, and automation of, testing: it's such a boring, repetitive activity that not automating would reduce the testing quality and efficacy significantly. Not only that, automation reduces the actual testing time, directly impacting resource costs. Not all tests can be automated of course and those are the ones that need careful monitoring. I did use to have the argument with less experienced colleagues along the lines of "whilst we're creating these tests, we could just be getting one with it" but not for very long. I also used to have an internal philosophical dialog along the lines of "who's testing the tests and do we need to create tests to test the tests" but then I went insane and other voices took over 
