November 16, 2007 11:19 pm

Enough Time and Buddy Testing for a quality output

Filed under: Computers,Exploratory Testing,Internet,Software Testing — ramsblog @ 11:19 pm

Give time to your team to be creative and teams do the miracles. Well, it depends – you may say. This was my recent experience and I have experienced a few times before in our application development processes. Several years ago, when we first implemented the buddy testing for couple of applications, teams followed these steps

a.       Both dev and test get-together to discuss about the approach

b.      Dev team wrote the code while test team wrote the various scenarios to test a piece of application

c.       Dev completed the code with a unit testing as much as possible (no, it was not a TDD back then)

d.      Test team did a buddy testing on that piece of code

e.      Code integrated later on and released to the functional testing.

f.        Functional test team did a thorough testing on a new environment à resulting in no defects found in this environment .

5 key positive things happened during this course:

1.       Dev and test collaboration increased

2.       Dev and test teams were on the same page with respect to requirements

3.       Most defects were found as part of the buddy testing and the feedback was passed on to the dev team right then. This resulted in quality code released to the functional test, and saving the cycle time during the functional testing phase.

4.       Since dev folks been open as part of this collaboration, and increased the thought process and increased the programming quality over time.

5.       Built a Trust relationship between dev and test teams à resulting in more open and honest in accepting criticisms and better feedback comments.

Apparently, we had our team members going through similar exercises lately, and seeing better results in building the quality code. I could tell, there was more sense of satisfaction between the teams for getting things done in right way than keeping eye on the bug counts and keeping the defects slip through different functional phases.

Guidelines for Buddy Testing:

We didn’t have any specific guidelines however, we did make it up during the process.

a.       Scripted test scenarios with necessary steps and prep data

b.      Used a Heuristics cheat sheet [link] for data type scenarios

c.       Performed more functional work flow scenarios than we had scripted for.

d.      Run through the scenarios to cover the code path to some extent (note: it is a fine line, but we had scoped it for mere UI testing)


a.       Quick turnaround during functional testing phase

b.      User Acceptance Testing team was happy

c.       Ultimate end users were satisfied with the product they received

Next Steps that would be ideal to these dev/test teams:

a.       Other area to explore into would be TDD (Test Driven Development)

b.      Agile project management viz., SCRUM

c.       Leverage code between dev and test teams and build better automation




  1. Interesting …. i too have have been involved in an ‘agile’ environment like you describe (in fact that’s what the company i work for does well – we also have a couple of our people become certified SCRUM masters)…it is great when there is synergy between developers and testers – not conflict. Like yourself, you’ve probably seen what happens when contention exists and i guarantee that quality of product would not be as great as if there is some sort of collaboration. Now of course we testers still reserve the right to be ‘critical’, sceptical and downright against what is being developed if it is justified but in saying that, when trust exists, the will to produce top quality work increases.
    Thanks for the blog!

    Comment by bjosman — November 27, 2007 11:43 am @ 11:43 am | Reply

  2. what is meant by bug realease?

    Thanks in advance

    Comment by murthy — March 13, 2008 10:27 pm @ 10:27 pm | Reply

RSS feed for comments on this post. TrackBack URI

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: