STE QUESTION BANK

1. Define software testing, failure, error, fault, defect.

Software Testing : Software Testing is the process of executing a program
with the intent of finding errors.
Error: A human action that produces an incorrect result.
Fault: An incorrect step, process, or data definition in a computer program.
Failure: A failure is said to occur whenever the external behavior of a
system does not conform to that prescribed in the system specification. A
software fault becomes a software failure only when it is activated.
Defect: A defect is an error in coding that causes a program to fail or to
produce incorrect /unexpected results.

2. List the objectives of software testing.

1. Finding Errors: Testing is process of executing a program with an
intention of finding an error.
2. Creating good test cases: A good test case is one that has a high
probability of finding yet undiscovered error.
3. Quality Improvement : Defects are fixed by the developer, so quality is
improved.
4. Satisfying customer requirements: Testing demonstrates to the
customer that software works properly as per specification.

3. Explain any 4 testing Principles.

1.Testing Shows the Presence of Defects - Testing can show the defects
are present, but cannot prove that there are no defects. Even after testing
the application thoroughly, we cannot say that the product is 100% defect
free.
2. Early Testing - The cost involved in fixing defects in the early stages is
very less when compared to those
that are found during the later stages of testing.
3. Exhaustive Testing is Not Possible - It is not possible to test all the
functionalities with all valid and invalid combinations of
input data during actual testing. Instead of this approach, testing of a few
combinations is considered based on priority using different techniques.
4. Testing is Context-Dependent - Different domains are tested
differently, thus testing is purely based on the context of the
domain or application.
 STE QUESTION BANK
4. Explain when to start and stop testing.
Process model is a way to represent any given phase of software
development that prevent and minimize the delay between defect injection
and defect detection/correction.

Entry criteria, specifies when that phase can be started also included the
inputs for the phase. Tasks or steps that need to be carried out in that
phase, along with measurements that characterize the tasks.
Verification, which specifies methods of checking that tasks have been
carried out correctly. Clear entry criteria make sure that a given phase does
not start prematurely.
The verification for each phase helps to prevent defects. At least defects
can be minimized.

Exit criteria, which stipulate the conditions under which one can consider
the phases as done and included are the outputs for the phase.

Exit criteria may include:

1. All test plans have been run
2. All requirements coverage has been achieved.
3. All severe bugs are resolved.
 STE QUESTION BANK

Differentiate between Verification and Validation.

follows

Define software Quality Assurance and software Quality Control.

Quality Assurance : A set of activities designed to ensure that the

development and/or maintenance process is adequate to ensure a system
will meet its objectives.

Quality Control : A set of activities designed to evaluate a developed

work product.
 STE QUESTION BANK
7. Describe Boundary Value Analysis . What are three guidelines for
boundary value Analysis
Boundary Value Analysis (BVA) is a software testing technique used to
identify errors at the edges of input ranges.
It involves designing test cases that focus on values at the boundaries of
input limits (both valid and invalid).
By testing at these boundaries, BVA helps uncover defects that might not
be evident when testing within the typical range of inputs.
Example 1: A system can accept the numbers from 1 to 10 numeric values.
All other numbers are invalid values. Under this technique, boundary
values 0, 1,2,9,10,11 can be tested.

There are three guidelines for boundary value analysis :

1) One test case for exact boundary values of input domains.
2) One test case for just below boundary value of input domains .
3) One test case for just above boundary values of input domains

8. What is Equivalence partitioning . Explain with example

In equivalence partitioning the range is divided into various classes and
from each class you test a single value, if it is pass the full class is pass and
if it is fail the full class is fail. It saves time.

Example: For example, an OTP number which contains only six digits,
less or more than six digits will not be accepted, and the application will
redirect the user to the error page.
STE QUESTION BANK
 STE QUESTION BANK

11. Write any four test cases to test login form.

 STE QUESTION BANK

12. Describe levels of testing.

There are mainly four testing levels are:
1. Unit Testing : testing the individual units/component of a
software/system is tested.
2. Integration Testing- individual units are combined and tested as a
group.
3. System Testing-complete integrated system / software is tested
4. Acceptance Testing :test the final system for acceptability
 STE QUESTION BANK

13. Explain unit test considerations with a neat diagram.

Explanation
Module interface - information properly flows into and out of the
program unit
under test.
Local data structure - data stored temporarily maintains its integrity.
Boundary conditions - module operates properly at boundaries
established to
limit or restrict processing.
Independent paths - all statements in a module have been executed at
least
once.
And finally, all error handling paths are tested.

Additional Requirements : The module under consideration might be

getting inputs
from another module or the module is calling some another module .
Some interface modules has to be simulated if required like drivers and
stubs.
 STE QUESTION BANK
14. What are drivers and stubs.
Drivers: The module where the required inputs for the module under test
are simulated for the purpose of module or unit testing is known as a
Driver module. The driver module may print or interpret the result
produced by the module under test.
Stubs: The module under testing may also call some other module which
is not ready at the time of testing. There is need of dummy modules
required to simulate for testing, instead of actual modules. These are called
stubs.

15. What is test plan?

A test plan is a document that describes the scope, approach, resources and
schedule required for conducting testing activities
The test plan acts as the anchor for the execution, tracking and reporting of
the entire testing project.

16. What are the Activities of test plan?

1. Scope Management: Deciding what features to be tested and not
to be tested.
2. Deciding Test approach /strategy: Which type of testing shall be
done like configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit
criteria for different phases of testing. The test strategies for the various
features and combinations determined how these features and
combinations would be tested.
4. Identifying responsibilities, staffing and training needs.