Skip to main content

The Defect Dance

When you find a defect in your test environment, it's always a nice feeling. You've managed to discover something that likely no one has discovered before.

 When you discover a defect, what do you do next? Do you just raise a defect, after all the team needs to hear about how awesome you are, do you speak to a developer.... Here's a handy little guide that you can use to ensure that you are as effective as possible as a QA.

 Ask yourself the following questions:
  • Is the bug reproducible?
    • If the answer is yes, then you've found a bug! 
    • If no, then I find it useful to make a mental note of the issue in case it happens again...
  • Is the bug in live?
    • If the answer to this is yes, then search the bug database, it may already have been logged, if it hasn't then raise a support issue or raise a bug, depending on what the company procedure is :)
    • If the answer is no, then still, check to see if the bug is a reoccurring bug and if it had been fixed previously and broke again, if the answer is yes, then raise a new bug and ensure there is an associated test case created to catch the bug again, if no raise a defect :) 
    • If it isn't a reoccurring bug then ask yourself (if you have domain knowledge) and speak to a developer, can the bug be fixed quickly, if it can then just liaise with the developer over the bug and let them fix it without raising a bug (there will be more about this in later posts, over when to raise a defect... ) if it can't, then go ahead, log a bug!

I've tried to summarise the above in a quick flow diagram below...


Obviously this won't work for every company, for example: if you're working on a brand new feature, the bug won't be in live so you can skip  that step...  However, I think it's a pretty useful set of questions that can help you decide what to do with a defect.

If anyone has anything to add to the defect dance or if you think there's a step that doesn't necessarily need to be there, then let me know! :)






Labels:

Comments

  1. Amar G Deogirikar10 May 2013 at 14:14

    I actually tried to make a similar version of defect dance, based on your idea. This is how it looks http://i.imgur.com/s65MaqE.png

    It is not very far from what you have!

    ReplyDelete
    Replies
    1. Gareth Waterhouse14 May 2013 at 02:20

      Cool! I must admit though, I'd spend a bit more time if I can't recreate it first time, as I mentioned in future blog posts explaining why etc.

      Delete

Post a Comment

Popular posts from this blog

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more