Chapter-Testing: The Various Levels of Testing Are

CHAPTER-
TESTING
The various levels of testing are:
1. White Box Testing
2. Black Box Testing
3. Unit Testing
4. Functional Testing
5. Performance Testing
6. Integration Testing
7. Objective
8. Integration Testing
9. Validation Testing
10. System Testing
11. Structure Testing
12. Output Testing
13. User Acceptance Testing

White Box Testing:
Execution of every path in the program.
Black Box Testing:
Exhaustive input testing is required to find all errors.

Unit Testing:

Unit testing, also known as Module Testing, focuses verification efforts on
the module. The module is tested separately and this is carried out at the
programming stage itself.
Unit Test comprises of the set of tests performed by an individual
programmer before integration of the unit into the system.
Unit test focuses on the smallest unit of software design- the software
component or module.
Using component level design, important control paths are tested to
uncover errors within the boundary of the module.
Unit test is white box oriented and the step can be conducted in parallel for
multiple components.

Functional Testing:
Functional test cases involve exercising the code with normal input values
for which the expected results are known, as well as the boundary values

Objective:
The objective is to take unit-tested modules and build a program structure
that has been dictated by design.

Performance Testing:
Performance testing determines the amount of execution time spent in
various parts of the unit, program throughput, and response time and
device utilization of the program unit. It occurs throughout all steps in the
testing process.

Integration Testing:
It is a systematic technique for constructing the program structure while at
the same time conducting tests to uncover errors associated with in the
interface.
It takes the unit tested modules and builds a program structure.
All the modules are combined and tested as a whole.
Integration of all the components to form the entire system and a overall
testing is executed.

Validation Testing:
Validation test succeeds when the software functions in a manner that can
be reasonably expected by the client.
Software validation is achieved through a series of black box testing which
confirms to the requirements.
Black box testing is conducted at the software interface.
The test is designed to uncover interface errors, is also used to demonstrate
that software functions are operational, input is properly accepted, output
are produced and that the integrity of external information is maintained.

System Testing:
Tests to find the discrepancies between the system and its original
objective, current specifications and system documentation.

Structure Testing:
It is concerned with exercising the internal logic of a program and
traversing particular execution paths.

Output Testing:
Output of test cases compared with the expected results created
during design of test cases.
Asking the user about the format required by them tests the output
generated or displayed by the system under consideration.
Here, the output format is considered into two was, one is on screen and
another one is printed format.
The output on the screen is found to be correct as the format was designed
in the system design phase according to user needs.
The output comes out as the specified requirements as the users hard
copy.

User acceptance Testing:

Final Stage, before handling over to the customer which is usually carried
out by the customer where the test cases are executed with actual data.
The system under consideration is tested for user acceptance and
constantly keeping touch with the prospective system user at the time of
developing and making changes whenever required.
It involves planning and execution of various types of test in order to
demonstrate that the implemented software system satisfies the
requirements stated in the requirement document.

Two set of acceptance test to be run:

1. Those developed by quality assurance group.
2. Those developed by customer.

TEST CASES :

USECASE

DESCRIPTION

EXPECTED
EVENT

OBSERVED
EVENT

RESULT
Mobile Installing the
application
Installation
sucessful
Installation
sucessful
Yes
Speak User interacts
through voice
Voice
recognition
Voice
recognition
Yes
Voice
activity
detector
Detects the user
voice
Detection of
voice
Voice
detected
Yes
Automatic
speech
recognition
Converts speech to
text
Text is
obtained
Text is
obtained
Yes
Conversatio
nal engine
Extract exact
meaning
Command
obtained
Command
obtained
Yes
Text to
speech
Converts the
acknowledgement
from text to voice
Acknowledge
ment is
obtained in
form of voice
Acknowledge
ment is
obtained in
form of voice
Yes

Chapter-Testing: The Various Levels of Testing Are

Uploaded by

Copyright:

Available Formats

Chapter-Testing: The Various Levels of Testing Are

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter-Testing: The Various Levels of Testing Are

Uploaded by

Copyright:

Available Formats

CHAPTER-

You might also like