How many bugs in the software?

Hi All,

How many bugs in the software?

Let's read a story of Birbal (Birbal was an advisor in the court of Akbar and is very popular for his sharp intellect and sense of humour)

One day Akbar was strolling in his palace gardens with his dear minister Birbal. Many crows were flying around. The King enjoyed their flying. Just then he thought, that how many crows could be in his kingdom and immediately posed this question to Birbal.

Birbal thought a moment, then said, "They are ninety-five thousand, four hundred and sixty three (95, 463) crows in your kingdom, Huzoor." "How do you know that for sure?" the King asked. "You can get them counted, Huzoor." Birbal said.

The king again said, "If there will be less than that, then?" Birbal replied immediately, "That means that the rest of them have gone on vacation to some neighboring kingdoms." "Or if there were more than that, then?" "Then it means that other crows are visiting your kingdom, Huzoor."

I hope the story answers “How many bugs in the software?”

For more stories and to know more about Birbal Stories about Birbal

Please feel free to disagree with me, challenge me, discuss with me, by posting your comments. Also, feel free to reach me at sharu.b@gmail.com.

Disclaimer: All the blogs shared by me are my ideas, my thought, my understanding of the subject and does not represent any of my employer’s ideas, thought, plans or strategies.

Comments

ajai said…
A vague question merits a vague answer...

Precise question merits both precise and vague answers
May 8, 2008 at 12:22 PM
Shrini Kulkarni said…
>>>Precise question merits both precise and vague answers

Just as vague as when a managers asks "how good is the product" "Is it ready", "how many bugs are there" ...

Often we struggle with vague questions ... in software testing it is very common

Shrini
August 9, 2008 at 1:45 AM
Post a Comment

Popular posts from this blog

Exploratory testing, Session based testing, Scripted testing…concertedly

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some
Read more

What do you do when you find a bug?

What do you do when you find a bug? Hold on do not answer it right now. Let me first set the context. You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team? Or Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug id’s/descriptions? Or Walk to the developer share your notes; reproduce it if required, work together to identify the problem? I work in
Read more

Regression Checks + Regression testing = Regression testing?!

One of the questions I find hard to answer when I use exploratory test techniques in my project is,”How do you run regression tests? How do you prioritise them? Do you automate them? Do you document regression test cases?” And then a bunch of questions follow. Let me define the context. I work closely with developers; we use either Scrum or Kanban - which ever best suits our project, product owner, business. We do not believe in individual metrics, blame games, stringent processes, and heavy documentation. All we care about is to deliver high quality software. This does not mean that there is no process, metrics or documentation. We have them all, but they are there to meet our needs and to help those who will come onboard to support/maintain the software. Regression Checks At the start of a story, testers pair up with developers to develop feature files using SpecFlow. Some call it Acceptance Test Driven Development and others Behaviour Driven Development [I am yet to figure out the d
Read more