Skip to main content
You are not a member of this wiki.
Pages and Files
Test Automation Issues
Test Automation Patterns
Just a brief note about changes made. Feel free to comment on anything you see here.
August 2016: Seretta and Dot have decided to eventually eliminate the General Issues. They will stay for the time being, but we have been working on improving the Diagnostic so that it covers everything that is in General Issues but independently. We are also breaking up some of the longer questions and issues to make them easier to use. Please let us know any comments or reactions you have - thanks!
March 2016: Added new Execution Pattern
EXPECTED FAIL STATUS
and new Design Pattern
February 2016: Added new Management Pattern
December 2014, January 2015
KEEP AUTOMATION UP AND RUNNING
TEST AUTOMATION OWNER
Three new Management patterns added:
LOOK FOR TROUBLE
, KEEP AUTOMATION UP AND RUNNING and
Two new patterns added:
The general issues have now been linked into the home page for public use. Go to
to see these pages.
After working on the diagnostic pages for a few months, they have now been linked into the home page for general use. Go to
to see these pages.
Merged the issues
Work progressing on an alternative "way in" using Diagnostics.
We have added some mindmaps of individual patterns, showing the relevant issues, patterns used, and patterns that use it. We are wondering if this will make it a bit easier to see where you are! If you want to have a look, we have done
DESIGN FOR REUSE
GOOD PROGRAMMING PRACTICES
Lots of minor changes, and the mind maps all updated. Feedback from after Dot's email and LinkedIn appeal is incorporated. Some re-organisation, including making
a separate page. Added "how to add a new page" to
. Added some "how to get started" info to the Home page.
Re-organised categories so that there are four under both Issues and Patterns, and they are the same four. Issues that used to be in SUT-Testability were moved to Design and Process. Patterns that used to be in Development are merged with Design, with a few going to Execution Patterns. Issues created to reflect Michael Stahl's Failure Patterns, which are moved to a separate heading (they are really large issues - we would like to keep the word "pattern" for solutions).
Jennifer Leger added her experiences and useful advice to the patterns
GOOD DEVELOPMENT PROCESS
. Thanks very much!
We were very impressed by a presentation on Automation Failure Patterns, given by Michael Stahl, which Dot heard at Star East 2013. Michael has written up his thoughts and has agreed to let us include these failure patterns on this wiki. Thanks very much to Michael for his insights and for sharing here! See
19 April 2013
Changed the issue
(better description of what we are describing).
Merged the issue
OBSCURE TECHNICAL REPORTS
INEFFICIENT FAILURE ANALYSIS
Changed the pattern RIGHT AUTOMATION TEAM to
. Still not sure this is the best name for this pattern!
16 April 2013
Merged AUTOMATION STAGNATION with
This wiki was created on the 28th January 2013 by Seretta Gamba and Dorothy Graham. Over the next months, patterns and issues were added from the book that Seretta had produced as a Word document (inspired by stories from the book Experiences of Test Automation, by Dorothy Graham and Mark Fewster, published 2012. Seretta contributed Chapter 21 to this book.)
help on how to format text
Turn off "Getting Started"