Please enable JavaScript.
Coggle requires JavaScript to display documents.
C2 : Software Testing Life Cycle (Test Level (System Test (Test Basis…
C2 : Software Testing Life Cycle
SDLC Models
V- model
Requirement Definitions
Acceptance Testing
Functional System Design
System Testing
Technical System Design
Integration Testing
Component Specification
Component Testing
Programming
Iterative Development
Issues
Increase the range of test
Increase need for regression testing
every version need to test before release
Characteristic of Good Testing
The analysis and design of tests should begin during the corresponding development activity
Each test level has test objectives
Every development activity have a corresponding testing activity
Testers should be involved in reviewing documents as soon as drafts are available
Test Level
A group of test activities that are managed and organized together
Unit Test
Stub/Driver
Yes
Executed by Developer
Test Basis
Component Specification
Detailed Design
Data Model
Program Code
Test Object
Component
Program
Database Modules
Objectives
Finding defect in software components, that can be tested separately
Defect are fixed as soon as they are found
Verifies the functions of a software unit
Integration Test
Objectives
Finding defect in interfaces and in interactions between integrated components
Level
Component Integration
test integration between software component
perform after component test
System Integration
test interaction between different system
test interaction between hardware & software
perform after system testing
Test Basis
Software & System Design
Workflow
Architecture
Test Object
Interface
Infrastructures
System config data
Method
Top-Down
Pros
test interaction between different system
Cons
Critical problems at bottom level are discovered late
Bottom-Up
Pros
Good bug isolation
Cons
Critical problems at top level are discovered late
Big Bang
Cons
Hard to isolate bugs
Pros
Fast
System Test
Objectives
Verification if specified requirement are fulfilled by products
functional
non-functional
Scope
Address in test plan
Environment
As similar to final target as possible
To minimize risk of failure in real environment
Performed by
Independent Test Team
Test Basis
Functional Specifications
Use cases
Risk analysis report
Test Object
System, user, operation manual
System config & config data
Acceptance Test
Often the responsibility of the
customers
or
users
of a system
Objectives
to establish confidence in the system
assess the system’s readiness for deployment and use
it is not necessarily the final level of testing
Not to find defects
Acceptance testing may occur at various times in the life cycle
Level
User acceptance testing
Verify fitness for use by business users
Operational acceptance testing
Perform by system admin
Testing of backup/restore
Disaster recovery
User management
Contract & Regulation acceptance testing
acceptance criteria is defined when contact is agreed
To check if any regulation to government, legal or safety is adhere
Alpha & Beta testing
alpha
factory testing
test at developing org site
beta
field testing
test at customer site
Test Object
Form
Reports
Config Data
Test Basis
User requirement
System requirement
Risk analysis report
Test Type
Functional Testing
Consider the external behavior of the system
Non-Functional Testing
Test how the system works
Test the characteristics of a software products
to measure characteristics of systems and software that can be quantified on a varying scale
Structural Testing
Based on the architecture of software or system
To help measure the thoroughness of testing through assessment of coverage of a type of structure.
Retesting
A confirmation testing
Perform after modification to confirm defects are successfully remove
Regression Testing
Perform after changes made to discover any new defects uncovered
The extent of regression testing is based on the risk or Impact Analysis
Maintenance Testing
Triggered by
Modification
Planned enhancement
Corrective & emergency changes
Changes of environment
Migration
Operational test of new environment
Retirement
Data migration
Data Archiving
Scope
Risk of change
Size of change
Size of existing system
Issues
Specification is missing or out of date
Tester with domain knowledge is unavailable