Automation Courses
Test & Automation Consulting LLC is proud to offer the following two
training courses on software test automation. These have been presented
from coast to coast to very favorable reviews. Any organization
planning a full-out effort at automation should consider bringing in
these two days of training for all personnel involved - including
management.
The first day of training is non-technical. We discuss why test
automation projects have failed, and then move into the necessary
conditions needed to make the automation project succeed. Throughout
the first day, Jamie L. Mitchell shares the benefit of his vast
automation experience discussing many different areas that organizations
planning on succeeding in automation need to know. The second day, he
discusses the technical aspects of making automation work, from
architectures to actual coding patterns that he has used over the years
using all of the commercial automation tools.
Please contact Jamie L. Mitchell at sales@go-tac.com for pricing and
scheduling information.
Courses
- Software Test Automation: Principles of Success
Test automation has become something that we all think we want; it sure would be nice if we all knew what it meant. Unfortunately, many in the software quality field (and their managers) do not. When it comes to understanding automation, many of us are blind persons describing the elephant. Not knowing what automation really is may be a critical problem for your organization; especially if you are prepared to spend many thousands of dollars purchasing tools. The belief that automation is the ?testing silver bullet? has cost companies throughout the world untold millions (perhaps billions) of dollars.
- Software Test Automation: Architectures and Advanced Techniques
Your organization has decided that test automation is a good idea. You bought the commercial automation tool, taken the 3 day course that purports to teach you how to use the tool. So what do you do now?
Many organizations start the long paved path to automation hell by starting to create scripts using the Record / Playback mechanism supplied by the tool. Your automation program is now officially dead; it just doesn't know it yet. This common problem is understandable; the tool vendor sold it as an R/P tool.
