RSS

Testing in Agile – seperate or integrated?

08 Mar

I’ve been thinking about how to organise testing within an iteration. The challenge is that activities within an iteration are particularly related to a specific story. However, there are aspects of testing that are larger than a single story (e.g. integration testing). There are testing activities that are related to more than a single iteration (e.g. system and regression testing). I’ve seen models mooted where there is a parallel test iteration. This concerns me as it seems to split out testing (again) and has the potential to remove the emphasis on testing from the development aspects of the product. The risk is that the testers are once again excluded from the intra-iteration activities and lose visibility of what is occurring and what knowledge is being transferred. Another model I have seen is a specific test iteration as part of the overall release plan for the product. But is this not just “waterfall” by another name? What approach do we take that allows us to truly integrate testing into the agile iteration?

My thoughts?

1. include the testers in all core team activities from story elicitation through to unit testing

2. ensure that test automation is considered up front and time is allocated to automating the testing

3. ensure that Integration, System and Acceptance tests are integrated as tasks within the iteration

However, does this mean that we slow down development or do less “new” work during the iteration.

What do you think?

Posted by Sharon Robson

Advertisements
 

2 responses to “Testing in Agile – seperate or integrated?

  1. Parimala Shankaraiah

    March 9, 2010 at 2:25 pm

    Hi Sharon,

    I have been part of explicit test iterations in the past. In my case, this occurred more as a result of too many backlogs in testing. However, making test iterations a regular norm ends up being complete waterfall. Once in a while, test iterations may work fine. But it is always better to work as a single engineering team (Dev,QA,PM etc) for better results.

    This is my take as a beginner in agile 🙂

    Regards,
    Parimala Shankaraiah

     
  2. Sharon Robson

    March 9, 2010 at 6:00 pm

    Hi Parimala,
    I agree – that is why I was surprised to see an approach that had a seperate testing sprint – running parallel to the “development” sprint in an agile plan I saw recently. I certainly favour the totally integrated approach.

    When I saw this proposal – and I started to think about it, and having test only sprints, I asked myself how the teams were defining “done” if they were leaving the testing until later??

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: