51. Explain how does a test coverage tool works?
The code coverage testing tool runs parallel while performing testing on the actual product. The code coverage tool monitors the executed statements of the source code. When the final testing is done we get a complete report of the pending statements and also get the coverage percentage.
52. Mention what is the difference between a "defect" and a "failure" in software testing?
In simple terms when a defect reaches the end customer it is called a failure while the defect is identified internally and resolved then it is referred as defect.
53. Explain how to test documents in a project that span across the software development lifecycle?
The project span across the software development lifecycle in following manner
- Central/Project test plan: It is the main test plan that outlines the complete test strategy of the project. This plan is used till the end of the software development lifecycle
- Acceptance test plan: This document begins during the requirement phase and is completed at final delivery
- System test plan: This plan starts during the design plan and proceeds until the end of the project
- Integration and Unit test plan: Both these test plans start during the execution phase and last until the final delivery
54. Explain which test cases are written first black boxes or white boxes?
Black box test cases are written first as to write black box test cases; it requires project plan and requirement document all these documents are easily available at the beginning of the project. While writing white box test cases requires more architectural understanding and is not available at the start of the project.
55. Explain what is the difference between latent and masked defects?
- Latent defect: A latent defect is an existing defect that has not caused a failure because the sets of conditions were never met
- Masked defect: It is an existing defect that has not caused a failure because another defect has prevented that part of the code from being executed
56. Mention what is bottom up testing?
Bottom up testing is an approach to integration testing, where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
57. Mention what are the different types of test coverage techniques?
Different types of test coverage techniques include
- Statement Coverage: It verifies that each line of source code has been executed and tested
- Decision Coverage: It ensures that every decision in the source code is executed and tested
- Path Coverage: It ensures that every possible route through a given part of code is executed and tested
58. Mention what is the meaning of breadth testing?
Breadth testing is a test suite that exercises the full functionality of a product but does no