Golden Rules of Testing

This content is syndicated from Agile Testing | Tester Troubles by Ray Claridge. To view the original post in full, click here.

In a previous post I've blogged about switching from waterfall to agile and how this impacts us testers.

It's true, the change can be difficult for some of us. However, fear not, somethings never change regardless of the development approach.

I've put together, what I think are the golden rules of testing that still apply. So when someone says "that's not how we do it in agile" (and believe me - they will) don't take none of it and stick with the basics.

Read these simple golden rules for software testing based on my own experiences.

Its all about finding the bug as early as possible:
  • Start the software testing process by analysing requirements long before development.

Make sure you have these 3 software testing levels
  • Integration testing (performed by IT)

  • System testing (performed by professional testers)

  • Acceptance testing (performed by business users)

Don’t expect too much of automated testing:
  • First let me state this : automated testing can be extremely useful and can be a real time saver. But it can also turn out to be a very expensive and invalid solution.

Deal with resistance:
  • If you like to be instant popular, don’t become a software tester ! You 'll find out that you are going to meet a great deal of resistance... It is very likely that you will end up being the sole defender of quality at a certain point. Other participants in the project will be tempted to go for the deadline, whatever the quality of the application is.

  • You should deal with this by reporting facts and figures in stead of opinions. It might take a while before your work colleagues appreciate the great job you're doing !

Do regression testing every new release
  • Okay, you've tested your new development successfully. Great. But do the features of the application that you didn't change still work ? You really should test this before going live.

Let real users test with real data
  • This one is obvious but who does it ?

  • You cannot beat real data.

Give defects a test severity status :
  • Critical (must have, no work around)

  • High (must have, work around possible)

  • Medium (not business critical, but wanted)

  • Low (nice to have)

Let product owners deceide if a defect is to be fixed based on business priority:
  • A bit obvious, but I've seen testers make this decision and assign business statuses

  • Actively use these statuses for reporting and follow up !

This might be the most difficult goal to achieve:
  • You should talk about exit and entry criteria with IT. When is software good enough to deliver to a test team ? Think about server errors, certain level of IT testing achieved, when and how to build...

  • Same goes for business. What quality do they expect ? Who is going to make decisions on when to go live ? Make sure it is not you. Your role should be advisory.

Focus on the software testing process, not on the tools:
  • There 's a lot of talking about test management software. Sure, they can be very helpful indeed. These tools probably will take a lot of work out of your hands... But don't forget : it 's you who has to define the testing process. No tool is going to do that for you ! Think thoroughly about how you 're going to organise your testing. You can be very successful by using basic tools like MS Excel.

Good luck


Leave a Reply

Your email address will not be published. Required fields are marked *

12 + 14 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”



To explore how we can help you, please get in touch