Posts Tagged ‘testing’

Agile Testing: A Practical Guide for Testers and Agile Teams

February 3, 2009

Wondering how to get testers engaged in agile development?
Wondering how to transition your QA team from a traditional testing cycle into an agile one?

Then look no further! My good friend and agile testing guru Janet Gregory and Lisa Crispin have just released their latest book:

Agile Testing: A Practical Guide for Testers and Agile Teams


In the book Janet and Lisa cover everything from organizational challenges to tips and tricks on how to get more of your tests automated. It’s a comprehensive overview of everything you will ever need to know about agile testing and a great read for those looking to transition traditional testing teams into more agile ones.

So if you are looking for one book which gives a really good view of a day in the life of an agile tester and valuable role they can play on agile teams, you should definitely check out Janet and Lisa’s new book.

Congrats again Janet and Lisa!

How to host a Bug Hunting Party – Part II

December 11, 2008

Last week, I showed you how to host your own Bug Hunting Party for developers. Well this week we hosted one for business, and while the feedback was completely different, both were valuable tools for improving the quality of our app.

Let me explain why having both outside developers and business trying to break your app is the best of both worlds.

Developers, developers

A lot of people think developers make poor testers. I think that’s rubbish. Some of the best testers I know are ace devs and I would pay cold hard cash to have these guys come and try to break my app. And that’s exactly what we did last week with stellar results.

You see outside developers (those not familiar with the business of your application) have great technical insight into the technology behind how your app is built. They will know what types of exploits you’ll face, what kind of validations you will need to do, and better yet be able to offer suggestions on how to handle any problems they find.

It’s like they are the security guards at the bank with the inside track.


They also have the added luxury of not really knowing how your app works from the business side. That’s an advantage because they won’t necessary start trudging down the happy path. They will take detours. They will try and do things you never thought of. You can watch them, see where they struggle, and listen for things that are confusing or don’t make sense.

Taking care of business

Business users on the other hand brings an entirely different perspective to testing. They don’t care about technology per se. They care about whether the bloody things works!

As a developer, you can stare at your application for months on end, and not see the forest through the trees. Sit someone from business down however and they can tell you in about 30 secs the 10 things that are wrong with your front page. That’s why we always have business test.

And data. Boy do they know data. When you load up you application with production data, business can tell in an instant if things are working correctly. They have a feel and touch built up that only comes with experience.

You need em both

Of course the ultimate scenario for bug hunting is when you get both parties (developers and business) trying to break your app. Most teams focus on the business (which is the right thing to do) but don’t forget that outside developers can make fine testers too.

So if you’ve done a Bug Hunt with one side of the family tree but not the other, consider inviting both. Developers and business together each bring something different to testing applications, and together form a great one two punch for improving the quality of your application.

Happy hunting!

A special thanks to our hunters

Cameron Young
David Chamberlain
Bill Low
Arthur Tam (hunted)


Quality has nothing to do with testing

June 10, 2008

When people hear the word quality, many of us instantly think of testing.

This shouldn’t be any surprise as the words, quality, testing, quality assurance, QA groups, testers are often lumped together when people discuss quality and software.

What is a surprise for some is how little testing has to do with quality.

Quality on software projects begins way before any tests are written or executed.

Quality begins the first day you start your project.

It begins the moment you engage your customers and figure out how you are going to work together.

It manifests itself every day by the manner in which you collaborate with team members, and the spirit and attitude you bring to the work place.

It’s doing simple things, like getting feedback on you product early and often.

It means managing your project, and setting expectations, so that there is enough time to do the really important stuff, and not worrying about the rest.

It means bringing your A-game every day. Getting knocked down, and then getting back up and coming in for more the next day.

I would do well to remind myself of this the next time I need to deal with a problem of ‘quality’.

AddThis Social Bookmark Button