software-testing11. What are different test levels?

There are four test levels

Unit/component/program/module testing

Integration testing

System testing

Acceptance testing

12. What is Integration testing?

Integration testing is a level of software testing process, where individual units of an application are combined and tested. It is usually performed after unit and functional testing.

13. What are the tables in test plans?

Test design, scope, test strategies , approach are various details that Test plan document consists of.

Test case identifier


Features to be tested

Features not to be tested

Test strategy & Test approach

Test deliverables


Staffing and training

Risk and Contingencies

14. What is configuration management?

Configuration management is the detailed recording and updating of information for hardware and software components. When we say components we not only mean source code. It can be tracking of changes for software documents such as requirement, design, test cases, etc.

When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more defects injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intention of configuration management is to track our changes if we have issues with the current system. Configuration management is done using baselines.

15. What is the difference between UAT (User Acceptance Testing) and System testing?

System Testing: System testing is finding defects when the system under goes testing as a whole, it is also known as end to end testing. In such type of testing, the application undergoes from beginning till the end.

UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determines whether the product wil meet the needs of its users.

16. How does a coverage tool work?

While doing testing on the actual product, the code coverage testing tool is run simultaneously. While the testing is going on, the code coverage tool monitors the executed statements of the source code. When the final testing is completed we get a complete report of the pending statements and also get the coverage percentage.

17. What is Fault Masking?

Error condition hiding another error condition.

18. What does COTS represent?

COTS – Commercial off The Shelf.

The purpose of which is allow specific tests to be carried out on a system or network that resembles as closely as possible the environment where the item under test will be used upon release.

Test Environment

What can be thought of as being based on the project plan, but with greater amounts of detail?

Phase Test Plan

19. Should testing be done only after the build and execution phases are complete?

In traditional testing methodology testing is always done after the build and execution phases.But that’s a wrong way of thinking because the earlier we catch a defect, the more cost effective it is. For instance, fixing a defect in maintenance is ten times more costly than fixing it during execution.

In the requirement phase we can verify if the requirements are met according to the customer needs. During design we can check whether the design document covers all the requirements. In this stage we can also generate rough functional data. We can also review the design document from the architecture and the correctness perspectives. In the build and execution phase we can execute unit test cases and generate structural and functional data. And finally comes the testing phase done in the traditional way. i.e., run the system test cases and see if the system works according to the requirements. During installation we need to see if the system is compatible with the software. Finally, during the maintenance phase when any fixes are made we can retest the fixes and follow the regression testing.Therefore, Testing should occur in conjunction with each phase of the software development.

20. When should testing be stopped?

It depends on the risks for the system being tested. There are some criteria bases on which you can stop testing.

Deadlines (Testing, Release)

Test budget has been depleted

Bug rate fall below certain level

Test cases completed with certain percentage passed

Alpha or beta periods for testing ends

Coverage of code, functionality or requirements are met to a specified point

Written by 

Leave a Reply

Your email address will not be published. Required fields are marked *