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

Agile Testing

  • Mar 12, 2013 · 5:30 PM
  • This location is shown only to members

Testing Moves the Project Forward

On traditional projects, testing is usually treated as a quality gate, and the QA/Test group often serves as the quality gatekeeper. It’s considered the responsibility of testing to prevent bad software from going out to the field. The result of this approach is long, drawn out bug scrub meetings in which we argue about the priority of the bugs found in test and whether or not they are sufficiently important and/or severe to delay a release.

On Agile teams, we build the product well from the beginning, using testing to provide feedback on an ongoing basis about how well the emerging product is meeting the business needs. This sounds like a small shift, but it has profound implications.

The adversarial relationship that some organizations foster between testers and developers must be replaced with a spirit of collaboration. It’s a completely different mindset.

-from Agile Testing Overview by Elisabeth Hendrickson

Lightning Talker - Chris Edwards

Lightning Talker - Bill Allen

'Acceptance Test-Driven Development'

Lightning Talker - Kieran Murphy

'Test-Driven Development'

Lightning Talker - Ralph Brown

'Exploratory Testing'

Want to be a Lightning Talker?

'Your talk goes here'

Join or login to comment.

  • Bill A.

    Very informative. There was a request for more presentations on testing. Thoughts?

    March 12, 2013

    • Brian C.

      I am very interesting in seeing what products and how people are integrating different automated testings solutions for Agile projects. I would also be curious to know what some peoples pit falls were, things to avoid, etc.

      March 14, 2013

    • Tina W.

      I, too, would like to have more discussions related to ATDD and TDD.

      March 25, 2013

  • Joshua H.

    I would like to open up a discussion on what tools people are using for writing and tracking test cases and whether or not they like them or not.

    March 14, 2013

    • A former member
      A former member

      Kiwi for iOS. I really enjoy it.

      March 14, 2013

  • Brian C.

    I have used Version One for Agile projects and Bugzilla for maintenance projects I liked both. Version One had a lot more total project tracking functionality. Bugzilla was better for updating the team on an ongoing basis of new defects and capturing a defects history.

    1 · March 14, 2013

  • Faustino M.

    Definitely met my expectations. Glad to have joined and looking forward to further meetups. Thanks to all the presenters.

    1 · March 12, 2013

  • Alex D.

    Sorry guys, something came up family wise. See you next time!

    March 12, 2013

  • Aaron S.


    March 12, 2013

  • A former member
    A former member

    Saw this too late to join. Hopefully next time

    March 11, 2013

23 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