Just a brief note about changes made. Feel free to comment on anything you see here.

March 2017: Removed the General Issues from the home page.

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 COMPARISON DESIGN

February 2016: Added new Management Pattern DEPUTY

December 2014, January 2015
Renamed KEEP AUTOMATION UP AND RUNNING to AUTOMATION DECAY.
New Pattern TEST AUTOMATION OWNER

November 2014
Three new Management patterns added: LOOK FOR TROUBLE, KEEP AUTOMATION UP AND RUNNING and LOOK AHEAD.

October 2014
Two new patterns added: LOCALISED REGIMES and DEFAULT DATA.

June 2014
The general issues have now been linked into the home page for public use. Go to General Issues to see these pages.

February 2014
After working on the diagnostic pages for a few months, they have now been linked into the home page for general use. Go to Diagnostic to see these pages.

January 2014
Merged the issues INADEQUATE TEAM and SKILL SHORTAGE to INADEQUATE TEAM.
Work progressing on an alternative "way in" using Diagnostics.

September 2013
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, DOMAIN-DRIVEN TESTING, GOOD PROGRAMMING PRACTICES, MAINTAINABLE TESTWARE, and OBJECT MAP.

August 2013
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 Acknowledgements a separate page. Added "how to add a new page" to WIKI-RULES. 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 AUTOMATION ROLES and GOOD DEVELOPMENT PROCESS. Thanks very much!

July 2013
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 Failure Patterns.

19 April 2013
Changed the issue TEAM BUILDING to SKILL SHORTAGE (better description of what we are describing).
Merged the issue OBSCURE TECHNICAL REPORTS into INEFFICIENT FAILURE ANALYSIS
Changed the pattern RIGHT AUTOMATION TEAM to AUTOMATION ROLES. Still not sure this is the best name for this pattern!

16 April 2013
Merged AUTOMATION STAGNATION with STALLED AUTOMATION.

January 2013
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.)