Académique Documents
Professionnel Documents
Culture Documents
Testing Life
cycle, Bug Life cycle
Day 4-Session 1
Lavanya.M
Software Testing Life
cycle
Test Plan
Test Design
Test Execution
Test Log
Defect Tracking
Report Generation.
Testing Plan
During this phase Test Strategy, Test Plan, Test Bed will
be created.
A test plan is a systematic approach in testing a system or
software.
The plan should identify:
• Which aspects of the system should be tested?
• Criteria for success.
• The methods and techniques to be used.
• Personnel responsible for the testing.
• Different Test phase and Test Methodologies
• Manual and Automation Testing
• Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
• Evaluation & identification – Test, Defect tracking tools
Test Design
During this phase
Build release
Receiving acceptance
Bug Life Cycle
Types of Testing
List of the different types of testing that can be implemented are listed below which
will be followed by explanations of the same
Black Box Testing
Usability Testing
White Box Testing
Install / Uninstall Testing
Unit Testing
Recovery Testing
Incremental Integration Testing
Security Testing
Integration Testing
Compatibility Testing
Functional Testing
Exploratory Testing
System Testing
Ad-hoc Testing
End-to-End Testing
Comparison Testing
Sanity Testing
Alpha Testing
Regression Testing
Beta Testing
Acceptance Testing
Mutation Testing
Load Testing
Conformance Testing
Stress Testing
Quality Assurance Testing
Performance Testing
Black Box Testing
It can also be termed as functional testing
Tests that examine the observable behavior of software as
evidenced by its outputs without referencing to internal
functions is black box testing
It is not based on any knowledge of internal design or code
and tests are based on requirements and functionality
In object oriented programming environment, automatic code
generation and code re-use becomes more prevalent, analysis
of source code itself becomes less important and functional
tests become more important
Test if a component conforms to specification
White Box Testing
This term is more often used interchangeably with ‘stress’ and ‘load’ testing
To understand the applications’ scalability, or to benchmark the performance
in a environment or to identify the bottlenecks in high hit-rate Web sites, this
testing can be used
This testing checks the run-time performance in the context of the integrated
system
This may require special software instrumentation
Ideally, these types of testing are defined in requirements documentation or
QA or Test Plans.
Usability Testing
Testing conducted when development and testing are completed and bugs
and problems need to be found before final release
It is ‘live’ testing in an environment not controlled by the developer.
Customer records the errors / problems reports difficulties at regular
intervals
Testing is conducted at one or more customer sites
Typically conducted by end-users or customers and not by programmers
or testers
Exercise
Testing efforts should be started only after the coding
is completed. True/False