|
 |
Home > Detail: Introduction of Automated Test to a Project
| | |
Introduction of Automated Test to a Project
By Elfriede Dustin/Jeff Rashka/John Paul
  
Summary: "In an attempt to do more with less, organizations want to test their software adequately, but as quickly as possible. Faced with this reality, software managers and developers have little choice but to introduce automated testing to their projects....The introduction of automated test tools helps to replace archaic and mundane manual test processes with a more professional and repeatable automated test environment, that promotes test engineer retention and improves test engineer morale."
This article appeared in Methods & Tools, Summer 1999 (pp. 11–15), available at http://www.autotestco.com. The text originally appeared in and is adapted from Automated Software Testing (sections of chapter 4), copyright AWL, all rights reserved, ISBN 0-20-43287. | | |
|
|
View Content Detail:
• XDD3180filelistfilename1.pdf (23 Kb)
About the Author
Elfriede Dustin (edustin@bna.com) works as a QA/Test Manager at BNA Software (http://www.bnasoftware.com). Elfriede is co-author of the book Automated Software Testing, and also co-authored the recently published book Quality Web Systems. Her Automated Software Testing white papers are posted on www.StickyMinds.com.
Jeff Rashka is a Senior Manager at Computer Associates in Washington DC where he heads up an organization responsible for providing application migration and modernization services for commercial and federal government clients. Jeff has a masters degree in Information Systems from George Mason University, and has performed as a manager on a multitude of significant information system and systems integration projects. System applications have included worldwide transportation asset management, enterprise information management, financial management, bar-coded inventory management and shipboard information systems. Jeff also has process improvement management experience implementing the guidelines contained within the Software Engineering Institute’s Capability Maturity Model (CMM).
John Paul has performed as a senior programmer/analyst on financial and budgeting systems as well as a host of other information systems. His software development leadership responsibilities have included system analysis and design, application prototyping, and application development using a number of different methodologies and programming techniques. His software development responsibilities have included application testing using automated test tools as well as the performing Year 2000 compliance testing.
Back to Top
|
|
| |
|
|
|
