Transcription of When Should a Test Be Automated? - Exampler …
{{id}} {{{paragraph}}}
Copyright 1998 by Brian Marick. All rights Should a Test Be Automated? Brian MarickTesting want to automate as many tests as I can. I m not comfortable running a test only if a programmer then changes the code and introduces a bug? What if I don t catchthat bug because I didn t rerun the test after the change? Wouldn t I feel horrible?Well, yes, but I m not paid to feel comfortable rather than horrible. I m paid to be cost-effective. It took me a long time, but I finally realized that I was over-automating, thatonly some of the tests I created Should be automated . Some of the tests I was automatingnot only did not find bugs when they were rerun, they had no significant prospect of doingso. Automating them was not a rational question, then, is how to make a rational decision. when I take a job as a contracttester, I typically design a series of tests for some product feature. For each of them, Ineed to decide whether that particular test Should be automated .
When Should a Test Be Automated? 2 cumbersome setup, but leave the rest to be done manually. Or you might have a manual test that’s carefully enough documented that it can readily be run again.
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}
Writing Maintainable Automated Acceptance Tests, Test, Of Automated Test, Automated, Benefits Analysis of Test Automation, MEDTRONIC AUTOMATED COAGULATION TIMER, Test Automation Architectures: Planning for Test, Automated endoscope reprocessors, Automated Neuropsychological Assessment, Automated Neuropsychological Assessment Metrics ANAM