Friday, February 7, 2020

SOFTWARE TESTING FOR DUMMIES: Exposed and Ridiculed - requirements- vs subject-oriented testing

Developing each test to verify a specific requirement (or small number of requirements) is the standard accepted (and often argued for) approach to automated functional testing.  Were we to apply this approach to any other industry, we would likely drive our company into bankruptcy as we a laughed out of our career.  And yet we insist on following these practices in the very industry which should be light-years ahead of any other industry.  During our session, we viewed a simplistic example of applying our widely accepted approach to the Automobile industry for purposes of crash testing. 

 

 

Craig A. Stockton | QA Automation Architect - Continuous Testing
M 253.241.1598
| cstockto@TEKsystems.com
1601 5th Avenue, Suite #800, Seattle, WA 98101

TEKsystems. Experience the power of real partnership.

 

 



This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply e-mail so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you

1 comment:

  1. Well...adding a PDF to the post obviously failed. I'll see what I can do about providing it from another source, and adding a link here.

    ReplyDelete