addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupsimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1outlookpersonJoin Group on CardStartprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

April: 9 Patterns in Automated Testing

  • Apr 10, 2013 · 6:30 PM
  • This location is shown only to members

Many of the problems we face in Automated Testing aren't unique.  They are problems we've seen before and will see again.  Knowing these patterns helps us more quickly understand what will and won't work in a given situation.  This presentation will go over 9 patterns in automated testing.  Most of them are domain independent -- they are common across different businesses, technology stacks, and architectures.

Join us to learn nine automated testing patterns and get access to many others.

About the speaker:

Paul Merrill is a Consultant and Trainer for Beaufort Fairmont.  He's spent the last 12 years developing applications for a wide range of industries, from Healthcare to Advertising to Mobile.  Paul spends his time working to "rid the world of bad code" through training and player-coach engagements working with companies to automate their testing efforts and use software engineering best practices.

Beaufort Fairmont is the software industry's source for automated testing player-coach engagements, consulting, and training.  Our engineers have a passion for simplifying the complicated process of automated testing, allowing companies to take advantage of the many benefits of automated quality assurance.  For more information, visit us at

Join or login to comment.

  • Harold M.

    Paul: Enjoyed the talk.

    Regarding the first two patterns:
    - A test only tests one thing,
    - with only one reason for failure.

    I would like a framework in which one failing feature results in only one failure.

    1/ If only one feature fails, then only one test fails.
    - All other tests that depend on the failing feature are skipped.
    - Tests that do not depend on the failing feature are still executed.
    2/ Tests for functionality required by a given test will be executed before the given test, to determine whether the given test should be executed.

    e.g., if login fails, only that test fails and there will be no attempt to execute any tests that depend on being able to login.

    Is there a tool/framework that supports this concept?

    April 10, 2013

    • Harold M.

      So it looks like Assume.assumeTrue(isLogi­nOk()) may be the answer. I still wish isLoginOK() could fail first and then not have to executed for all dependent tests, unless ... Is there a way to remember that isLoginOK() failed the first time it is executed and then just return false every other time it is called, without actually executing the test each time. I guess isLoginOK() could be a method on a singleton with a state. This looks promising. I guess the order in which the tests are executed is not that important.

      April 11, 2013

    • Harold M.

      Alas Eclipse has a defect that makes assumeTrue failures look like passed tests. So close! Maybe in the next release of Eclipse.

      April 13, 2013

  • Dan K

    1 · April 11, 2013

  • Tracey R.

    Excellent presentation. Its obvious Paul has done automated testing a time or two in his career. ;-P

    2 · April 10, 2013

  • Ryan

    Have to stick around at work today. Excited to be involved in the May meeting!

    1 · April 10, 2013

    • Melissa C.

      Sorry you can't make it this evening

      April 10, 2013

  • Dan K

    We'll be recording this meetup and hope to have the video posted sometime tomorrow!

    April 10, 2013

  • A former member
    A former member

    Bummed I can't make it but I'll definitely be there next time.

    April 10, 2013

  • A former member
    A former member

    Something came up, can't make this meeting. Definitely will make the next one!

    April 10, 2013

    • Melissa C.

      Thanks for letting us know! see you in May!

      April 10, 2013

  • Samta

    looking for web sessions.

    April 10, 2013

  • Alex R.

    Regional manager for a consultancy does Continuous Delivery enablement work. Interested in ideas for improving test automation in deployment pipelines.

    1 · April 8, 2013

  • Paul M.

    Looking forward to seeing everyone at Bronto on Wednesday!

    2 · April 5, 2013

  • Rajendra Prasad Reddy P.

    I am from India, How can I participate in this meeting, Could you provide some webinar or Video recordings of this Meeting Session

    March 22, 2013

    • Dan K

      Greetings Rajendra! We plan to have this and future meetups recorded and available online for people. I'll send out an email and tweet out the link once it is available. :)

      March 22, 2013

  • Nathan W.

    March 18, 2013

50 went

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy