- Software Testing: Interview Questions - Book Cover
- Software Testing: Interview Questions - Title Page
- Copyright Page
- What’s on the CD
- About this book (1/3)
- About this book (2/3)
- About this book (3/3)
- How to Read This Book
- Contents (1/2)
- Contents (2/2)
- Chapter 1 Software Testing Basics
- (B) In which software life cycle phase does testing occur?
- (B) Can you explain the PDCA cycle and where testing fitS IN?
- (B) What is the difference between white box, black box, and gray box testing?
- (B) What is the difference between a defect and a failure?
- (B) What are the categories of defects?
- (B) What is the difference between verification and validation?
- (B) How does testing affect risk?
- (B) Does an increase in testing always improve the project?
- (I) How do you define a testing policy?
- (B) Should testing be done only after the build and execution phases are complete?
- (B) Are there more defects in the design phase or in the coding phase?
- (B) What kind of input do we need from the end user to begin proper testing?
- (B) What is the difference between latent and masked defects?
- (B) A defect which could have been removed during the initial stage is removed in a later stage. How does this affect cost?
- (I) Can you explain the workbench concept?
- (B) What’s the difference between alpha and beta testing?
- (I) Can you explain the concept of defect cascading?
- (B) Can you explain how one defect leads to other defects?
- (B) Can you explain usability testing?
- (B) What are the different strategies for rollout to end users?
- (I) Can you explain requirement traceability and its importance?
- (B) What is the difference between pilot and beta testing?
- (B) How do you perform a risk analysis during software testing?
- (B) How do you conclude which section is most risky in your application?
- (B) What does entry and exit criteria mean in a project?
- (B) On what basis is the acceptance plan prepared?
- (B) What’s the relationship between environment reality and test phases?
- (B) What are different types of verifications?
- (B) What’s the difference between inspections and walkthroughs?
- (B) Can you explain regression testing and confirmation testing?
- (I) What is coverage and what are the different types of coverage techniques?
- (A) How does a coverage tool work?
- (B) What is configuration management?
- (B) Can you explain the baseline concept in software development?
- (B) What are the different test plan documents in a project?
- (B) How do test documents in a project span across the software development lifecycle?
- (A) Can you explain inventories?
- (A) How do you do analysis and design for testing projects?
- (A) Can you explain calibration?
- (B) Which test cases are written first: white boxes or black boxes?
- (I) Can you explain cohabiting software?
- (B) What impact ratings have you used in your projects?
- (B) What is a test log?
- (I) Explain the SDLC (Software Development LifeCycle) in detail.
- (I) Can you explain the Waterfall Model?
- (I) Can you explain the Big-Bang Waterfall Model?
- (I) Can you explain the Phased Waterfall Model?
- (I) Explain the Iterative model, Incremental model, Spiral model, Evolutionary Model and the V-Model?
- (I) Explain Unit Testing, Integration Tests, System Testing and Acceptance Testing? (1/2)
- (I) Explain Unit Testing, Integration Tests, System Testing and Acceptance Testing? (2/2)
- (I) What’s the difference between System Testing and Acceptance Testing?
- (I) Which is the best model?
- (I) What group of teams can do software testing?
- Chapter 2 Testing Techniques
- (B) Can you explain boundary value analysis?
- (B) What is a boundary value in software testing?
- (B) Can you explain equivalence partitioning?
- (B) Can you explain how the state transition diagrams can be helpful during testing?
- (B) Can you explain random testing?
- (B) Can you explain monkey testing?
- (B) What is negative and positive testing?
- (I) Can you explain exploratory testing?
- (A) What are semi-random test cases?
- (I) What is an orthogonal arrays?
- (I) Can you explain a pair-wise defect?
- (I) Can you explain decision tables?
- (B) H ow did you define severity ratings in yourproject?
- Chapter 3 The Software Process
- Chapter 4 CMMI
- (B) What is CMMI and what’s the advantage of implementing it in an organization?
- (I) What’s the difference between implementation and institutionalization?
- (I) What are different models in CMMI?
- (I) Can you explain staged and continuous models in CMMI?
- (I) Can you explain the different maturity levels in a staged representation?
- (I) Can you explain capability levels in a continuous representation?
- (I) Which model should we use and under what scenarios?
- (A) How many process areas are present in CMMI and what classification do they fall in?
- (B) Can you define all the levels in CMMI?
- (I) What different sources are needed to verify authenticity for CMMI implementation?
- (I) Can you explain the SCAMPI process?
- (I) How is appraisal done in CMMI?
- (I) Which appraisal method class is best?
- (I) Can you explain the importance of PII in SCAMPI?
- (A) Can you explain implementation of CMMI in one of the Key process areas?
- (B) What are all the process areas and goals and practices?
- (A) Can you explain all the process areas?
- Chapter 5 Six Sigma
- (B) What is Six Sigma?
- (I) Can you explain the different methodology for the execution and the design process stages in Six Sigma?
- (I) What are executive leaders, champions, master black belts, green belts, and black belts?
- (I) What are the different kinds of variations used in Six Sigma?
- (A) Can you explain standard deviation?
- (B) Can you explain the fish bone/Ishikawa diagram?
- Chapter 6 Metrics
- (B) What is meant by measures and metrics?
- (I) Can you explain how the number of defects are measured?
- (I) Can you explain how the number of production defects are measured?
- (I) Can you explain defect seeding?
- (I) Can you explain DRE?
- (B) Can you explain unit and system test DRE?
- (I) How do you measure test effectiveness?
- (B) Can you explain defect age and defect spoilage?
- Chapter 7 Automated Testing
- (B) What are good candidates for automation in testing?
- (B) Does automation replace manual testing?
- (I) Which automation tools have you worked with and can you explain them briefly? (1/2)
- (I) Which automation tools have you worked with and can you explain them briefly? (2/2)
- (I) How does load testing work for websites?
- (A) Can you give an example showing load testing for Websites? (1/2)
- (A) Can you give an example showing load testing for Websites? (2/2)
- (I) What does the load test summary report contain?
- (I) Can you explain data-driven testing?
- (I) Can you explain table-driven testing?
- (I) H ow can you perform data-driven testing usingAutomated QA?
- Chapter 8 Testing Estimation
- (B) What are the different ways of doing black box testing?
- (B) Can you explain TPA analysis?
- (A) Can you explain function points?
- (B) Can you explain an Application boundary?
- (B) Can you explain the elementary process?
- (B) Can you explain the concept of the static and dynamic elementary processes?
- (I) Can you explain FTR, ILF, EIF, EI, EO, EQ, and GSC? (1/5)
- (I) Can you explain FTR, ILF, EIF, EI, EO, EQ, and GSC? (2/5)
- (I) Can you explain FTR, ILF, EIF, EI, EO, EQ, and GSC? (3/5)
- (I) Can you explain FTR, ILF, EIF, EI, EO, EQ, and GSC? (4/5)
- (I) Can you explain FTR, ILF, EIF, EI, EO, EQ, and GSC? (5/5)
- (A) How can you estimate the number of acceptance test cases in a project? (1/2)
- (A) How can you estimate the number of acceptance test cases in a project? (2/2)
- (A) Can you explain how TPA w orks?
- (A) How do you create an estimate for black box testing? (1/2)
- (A) How do you create an estimate for black box testing? (2/2)
- (A) How do you estimate white box testing?
- (A) Is there a way to estimate acceptance test casesin a system?
- Appendix A About the CD-ROM
- Index (1/2)
- Index (2/2)
- Back Cover
118 Software teSting interview QueStionS
(i) can you explain hoW the numBer of defects are
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
there 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.
The following are three simple tables which show the number of defects
SDLC phase-wise, module-wise and developer-wise.
n
n
Figure 112 Number of defects phase-wise
Figure 113 Number of defects module-wise
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.