.................................................................................................................Home / Back to Management Patterns / Back to Test Automation Patterns
Pattern summary
Start to automate as early as possible. The sooner automated tests can be run the sooner you can see results

Category
Management

Description
Start to automate as early as possible. The sooner you can run automated tests the sooner you can get results:
  • if you work side by side with the developers from the very beginning, you will be able to see to it that the Software Under Test (SUT) is developed as TESTABLE SOFTWARE
  • the developers have feedback from the beginning
  • Management will be more ready to support you if you show quickly a return on investment

Implementation
Start to automate a STEEL THREAD or AUTOMATE WHAT’S NEEDED.

Potential problems
If you support DATA-DRIVEN TESTING or KEYWORD-DRIVEN TESTING testers will be able to write automated test cases even before the SUT is fully implemented
Beware though of TOO EARLY AUTOMATION: you would invest a lot of effort to produce only “noise”!

Issues addressed by this pattern
HIGH ROI EXPECTATIONS

Experiences
If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!

.................................................................................................................Home / Back to Management Patterns / Back to Test Automation Patterns