Defect Management Software Testing Techniques

How come you find Defects, every time?

As part of one initiative, we (a group of testers) were assisting another project to complete its SIT cycle. Cycle-1 has already been completed, this was Cycle-2 with some enhancements. Finding defects in already-tested code is always a challenge.

Me: Got 4 defects in flow-1 day before yesterday.

Me: Got 5 defects in flow-2 yesterday.

Me: Got just 2 defects today L

Manager: How come you are able to find defects in already-tested flows?

How to Find Defects

I have a theory here.

  1. Developers have written the code keeping in mind the requirements, i.e. acceptance criteria. — check.
  2. QA already completed one round of SIT cycle. — check.

It can be inferred that primary functionality (the happy flows) should be working fine by now. Then why not try the alternate flows, corner cases, negative tests and invalid data? This is where developers are a bit slack 😉 😛 As an end-user there are numerous possibilities of inputting invalid data and then expecting correct behavior J After all, why do you think ‘Test data’ is so-so-important aspect of Software Testing 😉

Defects Lifecycle

  1. Go one module (or functionality) at a time.
  2. Quickly verify the happy flow.
  3. Check all the validations & expected errors using no/invalid data.
  4. Make sure you have covered all functional flows (i.e. options like Save, Edit, Submit, Cancel, Open, Close, Refresh, etc.)
  5. A tester’s ‘attention to details’ & ‘logical thinking’ comes in handy here.
  6. At last, do some ad-hoc tests with the intent of finding defects.

……………………………………………………………………….

Anurag Tandule | Sr. QA Engineer at Cybage Software

Exactly same thing happens with me. Then I choose to go with all the possible +ve n – ve scenarios along with ad-hoc testing, monkey testing (for UI) n as Nivedita mentioned Exploratory testing which caught some handsome issues.

……………………………………………………………………….

Nivedita Rai | Scrum Master & QA Lead at Al Tayyar Travel Group | Dubai

I agree to your point, adding my thoughts too. So here come agile in picture where we go with acceptance criteria, do all the possible testing, functional, end to end, positive/negative, regression, browser, devices, still at some point we see new issues comes in invariably.  My personal favorite is exploratory testing goes pretty well with agile before making any story as

Got some other tips & tricks? Please comment!

Looking for a Job Change in QA/Testing technology? Get Regular Job notifications @ WhatsApp!

Leave a Reply

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