Software Testing Questions & Answers (Compiled from UPSC, SSC ,PSC ,IBPS previous question papers)

Test Scenario: Test scenario is like laying out plans for testing the product, environmental condition, and number of team members required, making test plans, making test cases and what all features are to be tested for the product. Test scenario is very much dependent on the product to be tested. Test scenario is made before the actual testing starts.

Test Case: Test case is a document which provides the steps to be executed which has been planned earlier. It also depends on the type of product to be tested. Number of test cases is not fixed for any product.

1. Test Environment Test Bed

2. Test Environment S/W and H/W

3. Test Bed: Test Documents like Test Plan Document, Test Case Document.

4. Test Environment means

a. Test Bed installation and configuration

b. Network connectivity’s

c. All the Software/ tools Installation and configuration

d. Coordination with Vendors and others

Destructive testing includes methods where material is broken down in to evaluate the mechanical properties, such as strength, toughness and hardness. For example, finding the quality of a weld is good enough to withstand extreme pressure and also to verify the properties of a material.

Benefits of Destructive Testing (DT)

- Verifies properties of a material
- Determines quality of welds
- Helps you to reduce failures, accidents and costs
- Ensures compliance with regulations

High level Test cases are those which covers major functionality in the application (i.e. retrieve, update display, cancel
(functionality related test cases), database test cases).
Low level test cases are those which are related to UI related test cases.

The basic elements of Defect Report Format are:

1. Project name
2. Module name
3. Defect detected on
4. Defect detected by
5. Defect id
6. Defect name
7. Snapshot of the defect(if the defect is in the non reproducible environment)
8. Priority, severity, status
9. Defect resolved by
10. Defect resolved on

Testing Process:

1. Test requirements analysis

2. Creation of Test Strategy (Which includes creation of Test Cases)

3. Creation of Test Plans (Which includes Test Cases and Test Procedures)

4. Execution of test cases

5. Analyze the test results

6. Report the defects if any

Coverage is a measurement used in software testing to describe the degree to which the source code is tested. There are three basic types of coverage techniques as shown in the following figure:

- Statement coverage: This coverage ensures that each line of source code has been executed and tested.

- Decision coverage: This coverage ensures that every decision (true/false) in the source code has been executed and tested.

- Path coverage: In this coverage we ensure that every possible route through a given part of code is executed and tested.

Comparison Testing means comparing your software with the better one or you’re Competitor. While comparison Testing we basically compare the Performance of the software. For example If you have to do Comparison Testing of PDF converter(Desktop Based Application) then you will compare your software with your Competitor on the basis of:-

1. Speed of Conversion PDF file into Word.

2. Quality of converted file.

The difference between latent and masked defect are:

- A latent defect is an existing defect that has not yet caused a failure because the conditions that are required to invoke the defect is not meet.

- A masked defect is an existing defect that has not yet caused a failure just because another defect hides that part of the code from being executed where it is present.

Verification is static type of software testing which is started in earlier phase of development of software. In this approach we don’t execute the software that the reason it comes in static testing. The product is evaluated by going through the code. Types of verification are:

- Walkthrough: Walkthroughs are informal technique. Where the Developer leader organizing a meeting with team member to take feedback regarding the software. This can be used for the improvement of the software quality. Walkthrough are unplanned in the SDLC cycle.

- Inspection: Inspection is a done by checking of a software product thoroughly with the intention to find out defect and ensuring that software is meeting the user requirements.

There are three main categories of defects:

- Wrong: The requirements are implemented incorrectly in the application.

- Missing: When requirement given by the customer and application is unable to meet those application.

- Extra: A requirement incorporated into the product that was not given by the end customer. This is always a variance from the specification, but may be an attribute desired by the user of the product.

1. First we need to verify whether the radio button is there are not?

2. Conform the radio buttons are present after the customer address or not.

3. Verify the no of radio button.

4. Verify only one radio button should be checked initially when we open the Customer details form (if it is mentioned in FS)

5. Verify the functionality of the radio buttons i.e. if we check one ratio button, second radio button should be unchecked.

6. Verify the spell check of radio button label name.

7. Verify the alignment of radio buttons in the form.

Software testing is an important part of the software development process. In normal software development there are four important steps PDCA (Plan, Do, Check, Act) cycle. The four steps are discussed below:

- Plan: Define the goal and the plan for achieving that goal.

- Do: execute those plan strategy which is planned in plan phase

- Check: Check to make sure that everything is going according to the plan and gets the expected results.

- Act: Act according to that issue.

Software applications are made up by the help of several elementary processes. There are two types of elementary processes:

- Dynamic elementary Process: The dynamic elementary involves process of moving data from one location to another location. The location can be within the application and outside the application.

- Static elementary Process: Static elementary involves maintaining the data of the application.

Integration testing is black box testing. Integration testing focuses on the interfaces between units, to ensure that units work together to complete a specify task. The purpose of integration testing is to confirm that different components of the application interact with each other. Integration testing is considered complete, when actual results and expected results are same. There are mainly three approaches to do integration testing.

- Top-down Approach: Tests the components by integrating from top to bottom.
- Bottom-up approach: It takes place from the bottom of the control flow to the higher level components
- Big bang approach: In this are different module are joined together to form a complete system and then testing is performed on it.

- Verification is Static testing where as Validations is Dynamic Testing.

- Verification takes place before validation.

- Verification evaluates plans, document, requirements and specification, where as Validation evaluates product.

- Verification inputs are checklist, issues list, walkthroughs and inspection where as in Validation testing of actual product.

- Verification output is set of document, plans, specification and requirement documents where as in Validation actual product is output.