References
AM: Agile Manifesto (http://agilemanifesto.org])
AUaP: Applying UML and Patterns, An Introduction to Object-Oriented Analysis and Design and Iterative Development, Craig Larman, Pearson Education 2005, ISBN 0-13-148906-2
BrP:Breakthrough Performance: Managing for Speed and Flexibility, William R. Daniels, ACT Publishing 1995
DCTABC: Developing a compelling Test Automation Business case, Bob Galen http://www.compaid.com/caiinternet/ezine/Galen1.pdf
DP: Design Patterns: Elements of Reusable Object-Oriented Software, Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Addison-Wesley 1995, ISBN 0-201-63361-2
EPaMDA: Enterprise Patterns and MDA, Building Better Software with Archetype Patterns and UML, Jim Arlow and Ila Neustadt, (Addison-Wesley Object Technology Series), Addison-Wesley 2003, ISBN 0-321-11230-X
EPE: Extreme Programming Explained: Embrace Change, Kent Beck, (Addison Wesley XP Series)
Addison-Wesley 1999,ISBN 2
EReq: Exploring Requirements: Quality before Design, Donald D. Gauss & Gerald M. Weinberg, Dorset House Publishing, 1989.
ETA: Experiences of Test Automation, Case Studies of Software Test Automation, Dorothy Graham and Mark Fewster, Addison –Wesley 2012, ISBN 978-0-321-75406-6
FP (Failure Patterns): The Pathologies of Failed Test Automation Projects, Michael Stahl, ebook [[1]] available from EuroStar.
HGTS: How Google Tests Software, James Whittaker, Jason Arbon and Jeff Carollo, Addison –Wesley 2012, ISBN-13: 978-0-321-80302-3, ISBN-10: 0-321-80302-7
HPT: Happy Path Testing, http://www.sei.cmu.edu/library/assets/happy.pdf
JTP: Java Testing Patterns, Jon Thomas, Matthew Youg, Kyle Brown and Andrew Glover, Wiley Publishing 2004, ISBN 0-471-44846-X
OE: The Oregon Experiment, Christopher Alexander, Murray Silverstein, Shlomo Angel, Sara Ishikawa and Denny Abrams, Oxford University Press 1975, ISBN 978-0195018240
PL: A Pattern Language: Towns, Building, Construction, Christopher Alexander, Sara Ishikawa and Murray Silverstein with Max Jacobson, Ingrid Fiksdahl-King and Shlomo Angel, Oxford University Press 1977, ISBN 978-0195019193
RIDEC: Refactoring, Improving the Design of Existing Code, Martin Fowler with contributions by Kent Beck, John Brant, William Opdyke and Don Roberts, Addison-Wesley 2000, ISBN 0-201-48567-2
RtP: Refactoring to Patterns, Joshua Kerievsky, (Addison-Wesley Signature Series), Addison-Wesley 2005, ISBN 0-321-21335-1
SCMP: Software Configuration Management Patterns, Effective Teamwork, Practical Integration, Stephen P. Berczuk with Bras Appleton, (Addison-Wesley Software Patterns Series), Addison-Wesley 2003, ISBN 0201741172
Addison-Wesley 1999, ISBN 0-201-33140-3
TBPoTA:The Big Picture of Test Automation: Test Trustworthiness' – Alan Page, Microsoft (2012)
TOOS: Testing Object-Oriented Systems, Models, Patterns and Tools, Robert V. Binder, (Addison-Wesley Object Technology Series), Addison-Wesley 2000, ISBN 0-201-80938-9
TWB: The Timeless Way of Building, Christopher Alexander, Oxford University Press 1979, ISBN 978-0195024029
UITABP: UI Test Automation Best Practices], Filip Czaja (http://fczaja.blogspot.de/2011/01/ui-test-automation-best-practices.html)
xUTP: xUnit Test Patterns: Refactoring Test Code, Gerard Meszaros, (Addison Wesley Signature Series), Addison-Wesley 2007, ISBN 978-0131495050. See also http://xunitpatterns.com.
There is a book about automation patterns: MetaAutomation: a Pattern language for accelerating automation and communication for fast, actionable quality, by Matt Griscom, 2014. Matt describes five patterns, some of which are similar to patterns in this wiki:
"Atomic Check" is the same as INDEPENDENT TEST CASES.
"Precondition Pool" is related to ABSTRACTION LEVELS and FRESH SETUP
"Parallel Run" is like our GET ON THE CLOUD - use virtual machines.
"Smart Retry" addresses the problems of FLAKY TESTS. Our patterns EXPECTED FAIL STATUS, FAIL GRACEFULLY and VERIFY-ACT-VERIFY deal with similar problems.
"Automated Triage" covers points made in READABLE REPORTS.
I (Dot) have also seen an updated version (2018) with a few other patterns:
"Event-Driven Check" is the same as VARIABLE DELAYS.
"Prioritised Requirements" is covered by ABSTRACTION LEVELS and TOOL INDEPENDENCE.
"Queryable Quality" is covered by READABLE REPORTS.
"Extension Check" is something to do with non-deterministic outcomes for performance testing (but we don't cover performance testing in this wiki).
There are clearly parallels with our patterns, but unfortunately, I find the writing style in Meta-Automation difficult at best, so I don't recommend this book in its current form.