Scribd
Upload
967 views

Agilysys Interview Questions Apps and Technical

The document discusses topics related to manual testing including defect injection rate, defect review effectiveness, defect rate calculations, defect rejection ratio, defect leakage ratio, and defect detection efficiency. It also discusses test models and provides sample code for determining the number of tests required for decision coverage. Key points include: - Defect injection rate refers to the total number of known defects discovered in a product iteration. - Defect review effectiveness applies metrics to known defects to understand product quality. - Defect rate is the percentage of outputs that fail to meet quality targets and can be used to evaluate programs and processes. - Defect rejection ratio and defect leakage ratio are used to measure issues raised with no quality impact and issues

Uploaded by

priyada16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
967 views

Agilysys Interview Questions Apps and Technical

The document discusses topics related to manual testing including defect injection rate, defect review effectiveness, defect rate calculations, defect rejection ratio, defect leakage ratio, and defect detection efficiency. It also discusses test models and provides sample code for determining the number of tests required for decision coverage. Key points include: - Defect injection rate refers to the total number of known defects discovered in a product iteration. - Defect review effectiveness applies metrics to known defects to understand product quality. - Defect rate is the percentage of outputs that fail to meet quality targets and can be used to evaluate programs and processes. - Defect rejection ratio and defect leakage ratio are used to measure issues raised with no quality impact and issues

Uploaded by

priyada16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Aptitude Topics

 Quants

Technical for a web Manual tester

 3 Questions related to defect injection rate


Defect injection rate" refers to the number of defects that were discovered and reported during a
particular iteration of product development (ex: software program).  It is the total number of known
defects no matter whether they were discovered and immediately fixed or not.  

"Defect review effectiveness" applies metrics to the number and nature of known defects to better
understand the quality of a product.  

"Defect injection rate" would be used to determine "defect review effectiveness". 3*3 Defect rate
calculations and what scenario fits a better defect rate

 Defect rate/ Percentage of rejection


A defect rate is the percentage of output that fails to meet a quality target. Defect rates can be
used to evaluate and control programs, projects, production, services and processes.
Calculation
A defect rate is calculated by testing output for non-compliances to a quality target. Quality is
typically specified by functional and non-functional requirements. The following formula can be
used to calculate defect rate.
defect rate = (defects / output tested) x 100

 What is Defect Rejection Ratio (DRR) and Defect Leackage Ratio (DLR)?
- DEFECT REJECTION RATIO (DRR)DRR measures issues that were raised that ultimately had no
impact on product quality.  This could easily be considered a measure of wasted effort and an
opportunity for improvement.   DRR = # of defects rejected per tester; (assess tester performance)DRR =
# of defects rejected per module; (assess module complexity)DRR = # of defects rejected per team or
project; (assess overall performance)

- DEFECT LEAKAGE RATIO (DLR)DLR measures issues that were not identified during the test phase. 
Again, this is another opportunity for improvement.  DLR = # of defects missed per tester; (assess tester
performance)DLR = # of defects missed per module; (assess module complexity)DLR = # of defects
missed per team or project; (assess overall performance)

 Questions related to DDE

Definition
Defect Detection Efficiency (DDE) is the number of defects detected during a phase/stage that are
injected during that same phase divided by the total number of defects injected during that phase.
ELABORATION

 defects:
- Are confirmed and agreed upon (not just reported).
- Dropped defects are not counted.
 phase:
- Can be any phase in the software development life cycle where defects can be injected
AND detected. For example, Requirement, Design, and Coding.
 injected:
- The phase a defect is ‘injected’ in is identified by analyzing the defects [For instance, a
defect can be detected in System Testing phase but the cause of the defect can be due
to wrong design. Hence, the injected phase for that defect is Design phase.]

FORMULA

 DDE = (Number of Defects Injected AND Detected in a Phase / Total Number of Defects Injected
in that Phase) x 100 %

 Questions related to the model of testing


- For ex, Which model can be used if a defect from previous stage is bound to migrate to
the next stage which will lead to changes in base codes
- Given a scenario what is the best model to be approached v model or waterfall or RUP
or Rad or Agile

Given the following fragment of code, how many tests are required for 100% decision coverage?

if width > length

   thenbiggest_dimension = width

     if height > width

             thenbiggest_dimension = height

     end_if

elsebiggest_dimension = length  

            if height > length 

                thenbiggest_dimension = height

          end_if
end_if

Answer : 4

You have designed test cases to provide 100% statement and 100% decision coverage for the following
fragment of code. if width > length then biggest_dimension = width else biggest_dimension = length
end_if The following has been added to the bottom of the code fragment above. print "Biggest
dimension is " &biggest_dimensionprint "Width: " & width print "Length: " & length How many more
test cases are required?

None, existing test cases can be used

Question related to RTM and why it is used and best scenario when it is updated

How would you estimate the amount of re-testing likely to be required?

Metrics from previous similar projects and discussions with the development team

More questions topic are covered in below link

https://www.guru99.com/software-testing-interview-questions.html

You might also like