| || |
Abscence of Structured automated testing leads to.
A structured approach to automated testing is necessary to help steer the test team away from some of the common test program mistakes below:
• Implementing the use of an automated test tool without a testing process in place resulting in an ad-hoc, nonrepeatable, non-measurable test program
• Implementing a test design without following any design standards, resulting in the creation of test scripts that are not repeatable and therefore not reusable for incremental software builds
• Using the wrong tool
• Test tool implementation initiated too late in the application development life cycle, not allowing sufficient time for tool setup and test tool introduction process (i.e. learning curve)
• Test engineer involvement initiated too late in the application development life cycle resulting in poor understanding of the application and system design, which results in incomplete testing
• Not including software developers, so they can keep automated testing in mind when they make changes to the code. Developers need to understand the impact their code changes could have on an automated testing framework and can consider alternatives, as appropriate.
Re: Abscence of Structured automated testing leads
These are some great Tips/Observations, we can attest to every single one of your bullet points, and I've adapted them for a presentation for our next team meeting, thanks for posting this!