System Testing
Why System Testing
What do we Test For
Online Response
Volume
Stress Testing
Recovery & Security
Usability Documentation & Procedure
The Nature of Test Data
Artificial Data
Live Data
Activity N/W for System Testing
Prepare Test Plan
Specify Conditions for User Acceptance Testing
Prepare Test Data for Program Testing
Prepare Test Data for Transaction Path Testing
Plan User Training
Compile/Assemble Program
Prepare Job Performance Aids
Prepare Operational Documents
Prepare cross examination of what
you have thought at the start
Software Application Testing
A test plan is developed during the analysis phase .
During the design phase, a unit test plan and a
system test plan are developed .The actual testing is
done during implementation. Test plans provide
improved communication among all parties
involved in testing
Software Application Testing:
Types of Testing
Inspection
A testing technique in which participants examine
program code for predictable language-specific errors
Walkthrough
A peer group review of any product created during the
systems development process; also called a structured
walkthrough
Desk Checking
A testing technique in which the program code is
sequentially executed manually by the reviewer
Software Application Testing:
Types of Testing
Unit Testing
Each module is tested alone in an attempt to
discover any errors in its code, also called
module testing
Integration Testing
The process of bringing together all of the
modules that a program comprises for testing
purposes. Modules are typically integrated in a
top-down, incremental fashion
Software Application Testing:
Types of Testing
System Testing
The bringing together of all the programs that a system
comprises for testing purposes. Programs are typically
integrated in a top-down, incremental fashion
Stub Testing
A technique used in testing, especially where modules
are written and tested in a top-down fashion, where a
few lines of code are used to substitute for subordinate
modules
Software Application Testing:
The Testing Process
1. The purpose of the testing is confirming that the
system satisfies requirements
2. Testing must be planned
Test Case
A specific scenario of transactions, queries or
navigation paths that represent a typical, critical or
abnormal use of the system
Test cases and results should be thoroughly
documented so they can be repeated for each revision
of an application
Software Application Testing:
Acceptance Testing by Users
The process whereby actual users test a completed
information system, the end result of which is the
users acceptance of it
Black box testing
No knowledge of internal design or code
required.
Tests are based on requirements and
functionality
White box testing
Knowledge of the internal program design
and code required.
Tests are based on coverage of code
statements , branches , paths , conditions.
Black Box - testing technique
Incorrect or missing functions
Interface errors
Errors in data structures or external database
access
Performance errors
Initialization and termination errors
Black box / Functional testing
Based on requirements and functionality
Not based on any knowledge of internal
design or code
Covers all combined parts of a system
Tests are data driven
White box testing / Structural testing
Based on knowledge of internal logic of an
application's code
Based on coverage of code statements,
branches, paths, conditions
Tests are logic driven
Srihari Techsoft
White-box Testing
Methods based on the internal structure of
code:
Statement coverage
Branch coverage
Path coverage
Data-flow coverage
Functional testing
Black box type testing geared to functional
requirements of an application.
Done by testers.
System testing
Black box type testing that is based on overall
requirements specifications; covering all combined
parts of the system.
End-to-end testing
Similar to system testing; involves testing of a
complete application environment in a situation that
mimics real-world use.
Sanity testing
Initial effort to determine if a new software
version is performing well enough to accept
it for a major testing effort.
Regression testing
Re-testing after fixes or modifications of the
software or its environment.
White-box Testing
White-box methods can be used for
Test case selection or generation.
Test case adequacy assessment.
In practice, the most common use of white-box
methods is as adequacy criteria after tests have been
generated by some other method.
Software Application Testing:
Acceptance Testing by Users
Alpha Testing
User testing of a completed information system using simulated
data
Recovery testing
Forces the software (or environment) to fail in order to verify that
recovery is properly performed
Security testing
Verifies that protection mechanisms built into the system will protect
it from improper penetration
Stress testing
Tries to break the system
Performance testing
Determines how the system performs on the range of possible
environments in which it may be used
Software Application Testing:
Acceptance Testing by Users
Beta Testing
User testing of a completed information system
using real data in the real user environment
Quality Assurance
Correctness
Reliability
Efficiency
Usability
Maintainability
Testability
Portability
Accuracy
Error Tolerance
