Testing

6. SOFTWARE TESTING

Once source code has been generated, software must be tested to allow errors to be
identified and removed before delivery to the customer. While it is not possible to remove
every error in a large software package, the software engineer’s goal is to remove as many as
possible early in the software development cycle.

Software Testing Objectives:

 Testing is the process of executing a program with the intent of finding errors.
 A good test case is one with a high probability of finding an as-yet
undiscovered error.
 A successful test is one that discovers an as-yet-undiscovered error.

Software Testing Principles

 All tests should be traceable to customer requirements.

 Tests should be planned long before testing begins.
 Testing should begin in the small and progress to the large.
 Exhaustive testing is not possible.
 To be most effective, testing should be conducted by an independent third
party.

Good Test Attributes

 A good test has a high probability of finding an error.

 A good test is not redundant.
 A good test should not be too simple or too complex.

Two basic test techniques involve:

 Testing module input/output (black-box)

 Exercising internal logic of software components (white-box).

A.I.E.T, Gunthapally 45
 Testing

6.1. BLACK-BOX TESTING

Knowing the specified function that a product has been designed to perform, tests can
be conducted that demonstrates each function is fully operational, at the same time searching
for errors in each function. It enables us to derive sets of input conditions that will fully
exercise all function requirements for a program.
It attempts to find errors in the following categories:-

 Incorrect or missing functions

 Interface errors
 Errors in data structures or external database access
 Performance errors
 Initialization and termination errors

6.2. WHITE-BOX TESTING

This is performed knowing the internal workings of a product. Tests are conducted to
ensure that “all gears mesh”, that is, that internal operation performs according to
specification and all internal components have been adequately exercised. This can be done
on close examination of procedural detail by providing test cases that exercise specific set of
conditions and/or loops tests logical paths through the software.

Using the white-box testing we can derive test cases that,

 Guarantee that all independent paths within a module have been exercised at
least once.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds and
 Exercise internal data structures to assure their validity.

By the test cases each of the modules have executed at least once and tested for bugs.
All the logic decisions on their true and false sides are executed so that the system will
perform well.

A.I.E.T, Gunthapally 46
 Testing

6.3. UNIT TESTING

 Black box and white box testing.

 Module interfaces are tested for proper information flow.
 Local data are examined to ensure that integrity is maintained.
 Boundary conditions are tested.
 Basis path testing should be used.
 All error handling paths should be tested.
 Drivers and/or stubs need to be developed to test incomplete software.

 6.4. INTEGRATION TESTING

 Top-down integration testing

1. Main control module used as a test driver and stubs are substitutes for
components directly subordinate to it.
2. Subordinate stubs are replaced one at a time with real components (following
the depth-first or breadth-first approach).
3. Tests are conducted as each component is integrated.
4. On completion of each set of tests and other stub is replaced with a real
component.
5. Regression testing may be used to ensure that new errors not introduced.

 Bottom-up integration testing

1. Low level components are combined in clusters that perform a specific
software function.
2. A driver (control program) is written to coordinate test case input and output.
3. The cluster is tested.
4. Drivers are removed and clusters are combined moving upward in the program
structure.

A.I.E.T, Gunthapally 47
 Testing

6.5. VALIDATION TESTING

 Ensure that each function or performance characteristic conforms to its

specification.
 Deviations (deficiencies) must be negotiated with the customer to establish a
means for resolving the errors.
 Configuration review or audit is used to ensure that all elements of the
software configuration have been properly developed, cataloged, and documented to allow its
support during its maintenance phase.

Types of Validation Testing:

 Alpha Test
A customer conducts it at the developer’s site. The software is used in a natural
setting with the developer “looking over the shoulder” of the user and recording errors and
usage problems.

 Beta Test
This test is conducted at one or more users sited by the end user(s) of the
software. Here the developer is generally not present. Therefore, the beta test is a “live”
application of the software in an environment that can’t be controlled by the developer

A.I.E.T, Gunthapally 48
 Testing

Form Description Input Output Expected Action

Sno Name Output
Face Test Clicking on login Opens Opens login Keyboard/mouse
1 procedure: button login form form window
Case1: window
Consist of
login button
through which
we can go to
login form
window
2 Login Test Enter the Login fail We can open Keyboard /mouse
form procedure2: Numbers the main menu
Case1:
Consists of
user name and
password
Case2: Opens Keyboard/mouse
Consists of Enter the Opens Mainmenu
user name and Characters( userna Mainmenu window
password me=Archana and window
password=Archana)
Mainmenu Test Click on store Opens Opens Image Keyboard/mouse
3 procedure3: details Image window
Case1: window
Consists of 2
buttons: show
details and
store details

4 Image Test Click on get photo Keyboard/mouse

procedure4: button to get
Case1: images from files.
Consists of
three
buttons:get
photo,segment
and details
Case2:
Image When we click on The image The image is Keyboard/mouse
window segment button is cropped cropped in to
Case3: in to 3 3 parts
Criminal parts . This data
details When we click on This data will be stored Keyboard/mouse
details button will be in database
We can enter stored in when we click
details of criminals database on save
then click save when we button.(one
button. click on new entry will

A.I.E.T, Gunthapally 49
 Testing

save be created in
button. the database.)
5 File1 Test Click on next One part Full image is Keyboard/mouse
procedure5: button and when of image displayed after
Case1 we click on submit will be clicking on
Verification button appeared submit button
Of cropped
images
6 Details Test When we click on Details of Corresponding Keyboard/mouse.
procedure6: details button criminal details of
Case1 are criminal and
Expected retrieved image will be
details of a from displayed with
criminal database all expected
fields.

A.I.E.T, Gunthapally 50