Académique Documents
Professionnel Documents
Culture Documents
Objective
Spec
Spec
Design
Design
Build
Build
Test
Test&&Fix
Fix
* Here testing was happening only towards the end of the life
cycle
56%
56%
7%
7%
10%
10%
Source: IBM/TRW/Mitre
Ongoing
Support
Review/Test
High level
design
Operational
Testing
Integration
Testing
Detailed
Specifications
Unit Testing
Coding
STLC V Model
Requirement
Req. Review
Design
Design Review
Code
Code Review
Develop Unit Test
Review Unit Test
STLC Activities
Plan
Scope/Requirement
Approach
Process and Tools
Methodology
Delivery Models
Risk Plan
Project Overflow
Quality Objectives
Configuration Plan
Design
Test Design
Specifications
Test Scenarios
Test Cases
Test Data
Tool
Development
STLC Activities
Execution
Implement Stubs
Test Data Feeders
Batch Processes
Execute Testing
Collate Test Data
Identify Bugs
Defect Analysis
STLC Activities
Software Testing Life Cycle
Phase
Activities
Outcome
Planning
Analysis
Design
Construction
Testing cycles
Final testing
Post implementation
Test Approach
Test Process
conduct the
Test Approach
1. Requirement Analysis
2. Prepare Test Plan
3. Test Case Designing
4. Test Case Execution
5. Bug Reporting, Analysis and Regression testing
6. Inspection and release
7. Client acceptance and support during acceptance
8. Test Summary analysis
Requirement Analysis
Objective
The objective of Requirement Analysis is to
ensure software quality by eradicating errors as
earlier as possible in the developement process,
as the errors noticed at the end of the software
life cycle are more costly compared to that of
early ones, and there by validating each of the
outputs
The objective can be achieved by three basic issues:
Correctness
Completeness
Consistency
Type of requirement
Functional
Data
Look and Feel
Usability
Performance
Operational
Maintainability
Security
Scalability
Etc.
Evaluating requirements
Requirements Analysis
Difficulties in conducting requirement analysis
Design - Activities
Execution activities
Activities
Detect Bugs by executing test cases
Bug Reporting
Analyze the Error/Defect/Bug
Debugging the system
Regression testing
Client Acceptance
Software Installation
Provide Support during Acceptance Testing
Analyze and Address the Error/Defect/Bug
Track Changes and Maintenance
Final Testing and Implementation
Submission, client Sign-off
Update respective Process
Test Manager
Single point contact between onsite and offshore team
Prepare the project plan
Test Management
Test Planning
Interact with onsite lead, Client QA manager
Team management
Work allocation to the team
Test coverage analysis
Test Manager
Co-ordination with onsite for issue resolution.
Monitoring the deliverables
Verify readiness of the product for release through release review
Obtain customer acceptance on the deliverables
Performing risk analysis when required
Reviews and status reporting
Authorize intermediate deliverables and patch releases to
customer.
Test Lead
Resolves technical issues for the product group
Provides direction to the team members
Performs activities for the respective product group
Review and Approve of Test Plan / Test cases
Review Test Script / Code
Approve completion of Integration testing
Conduct System / Regression tests
Ensure tests are conducted as per plan
Reports status to the Offshore Test Manager
Test Engineer
Development of Test cases and Scripts
Test Execution
Result capturing and analysing
Defect Reporting and Status reporting
Automation Specialist
The ideal tester has deep insights into how the users will
exploit the programs features and the kinds of cockpit
errors that users are likely to make
The single most important quality for testers (just as for
programmers) is raw intelligence, good testers, just as
programmers, are smart people
Tolerate tedium
Comfortable with conflict
Report problems
Empirical
Whats observed
skeptic
People skills
developers,
lack
of
seriousness
among
Summary