Speed, Agility, Resilience
Trusted Experts in Microservices, Cloud Native & Chaos Engineering
  • Home
  • EBooks
  • Contact Us
  • Consultancy
    • One-to-One Online Consultancy
    • Onsite Consultancy
  • Training
    • One-to-One Online Training
    • Building Reliable Systems
    • Building Antifragile Systems with Microservices Course
    • Fast Track to Cloud Native Java
    • Fast Track to Applying DDD for Effective Microservices
    • Fast Track to Running Production Microservices
    • Fast Track to Chaos Engineering
    • Autumn of Cloud Native
  • Speaking
    • Schedule
    • Slides and Videos
    • Brown Bag Events
  • Blog
  • FAQ
  • Client Feedback
  • Gallery
  • (Print) Books
  • Essais

On the Origins of the Journey Pattern in Testing

8/20/2015

0 Comments

 
I was lucky enough to catch up with Antony Marcano, Andy Palmer and the venerable Jan Molak today.

After my post earlier this week on the early implementation of the Journey pattern in the Serenity BDD testing tool the guys wanted to share the early beginnings of the pattern that they had defined as early back as 2007!

So, for the record and prosperity, here's the history of the pattern! A huge thanks to the guys for sharing this with me and writing much of the narrative (thanks again Jan!).

The History of the Journey Pattern

The Journey Pattern concept arose from an idea that Antony Marcano (http://antonymarcano.com/blog) first demonstrated at the Agile Alliance Functional Test Tools workshop in 2007. 

It was later refined into JNarrate in 2009 with Andy Palmer's influence and incorporated into an experimental 'Narrative' FitFixture in 2009. Andy also introduced the idea of Soap Opera Personas (http://andypalmer.com/2014/03/soap-opera-personas/). 

It was refined further as a pattern and was used extensively in the financial industry after Antony introduced the JNarrate reference implementation to TimGroup. Following a presentation by Andy and Antony at CitCon 2009 TimGroup's Narratives project was born (https://github.com/tim-group/narrative). 

In 2012 Andy and Antony met Jan Molak (http://smartcodeltd.co.uk) who helped refine the general approach to assertions and added the final piece to the jigsaw puzzle, the name: The Journey Pattern.

The name of the pattern comes from the idea that we use Story Maps to navigate our projects and that a user goes on a number of journeys expressed by this map. 

Each example route we take is expressed as an acceptance test.
Note: This article has also been posted on Linkedin.com
0 Comments



Leave a Reply.

    Musings on software development

    Archives

    September 2017
    June 2017
    November 2016
    September 2016
    May 2016
    February 2016
    September 2015
    August 2015
    June 2015
    March 2015
    January 2015
    December 2014
    November 2014
    October 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    December 2013
    August 2013

    Categories

    All
    Announcements
    Antifragile
    Books
    Innovation
    Life Preserver
    Microservices
    Philosophy
    Psychology
    Reviews
    Software

    RSS Feed

Products

EBooks
​(Print) Books
Consultancy
Training
​
Speaking

Company

Essais
FAQ
Client feedback
Gallery

Support

Contact
Picture
© COPYRIGHT 2018. ALL RIGHTS RESERVED.


Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.