IndiaBIX

Software Testing - Metrics

Why should I learn to solve Software Testing: Metrics technical interview questions?

Learn and practise solving Software Testing: Metrics technical interview questions and answers to enhance your skills for clearing technical interviews, HR interviews, campus interviews, and placement tests.

Where can I get technical Software Testing: Metrics technical interview questions and answers with explanations?

IndiaBIX provides you with lots of fully solved Software Testing: Metrics technical interview questions and answers with a short answer description. You can download Software Testing: Metrics technical interview questions and answers as PDF files or e-books.

How do I answer Software Testing: Metrics technical interview questions from various companies?

You can answer all kinds of Software Testing: Metrics technical interview questions by practising the given exercises (short answer type). You can also find the frequently asked Software Testing: Metrics technical interview questions with answers from various companies, such as TCS, Wipro, Infosys, CTS, IBM, etc.

1.
What is meant by measures and metrics?
Measures are quantitatively unit defined elements, for instance, hours, km, etc. Metrics are basically comprised of more than one measure. For instance, we can have metrics such as km/hr, m/s etc.

Software Testing Image
2.
Can you explain how the number of defects is measured?
The number of defects is one of the measures used to measure test effectiveness. One of the side effects of the number of defects is that all bugs are not equal. So it becomes necessary to weight bugs according to their criticality level. If we are using the number of defects as the metric measurement the following are the issues:
  • The number of bugs that originally existed significantly impacts the number of bugs discovered, which in turns gives a wrong measure of the software quality.
  • All defects are not equal so defects should be numbered with a criticality level to get the right software quality measure.
3.
Can you explain unit and system test DRE?
DRE is also useful to measure the effectiveness of a particular test such as acceptance, unit, or system testing. The following figure shows defect numbers at various software cycle levels. The 1 indicates that defects are input at the phase and2indicates that these many defects were removed from that particular phase. For instance, in the requirement phase 100 defects were present, but 20 defects are removed from the requirement phase due to a code review. So if 20 defects are removed then 80 defects get carried to the new phase (design) and so on.

Software Testing Image
4.
Can you explain DRE?
DRE (Defect Removal Efficiency) is a powerful metric used to measure test effectiveness. From this metric we come to know how many bugs we found from the set of bugs which we could have found. The following is the formula for calculating DRE. We need two inputs for calculating this metric: the number of bugs found during development and the number of defects detected at the end user.

Software Testing Image

But the success of DRE depends on several factors. The following are some of them:
  • Severity and distribution of bugs must be taken into account.
  • Second, how do we confirm when the customer has found all the bugs. This is normally achieved by looking at the history of the customer.
Quick links
Quantitative Aptitude
Verbal (English)
Reasoning
Programming
Interview
Placement Papers