The document outlines the key components of the test process, including test planning, analysis, design, implementation, execution, and closure activities. It describes various test techniques like risk-based testing, test estimation, and reviews. The test process aims to define what to test through test conditions and how to test through concrete test cases. It helps deliver business value by managing quality costs and ensuring compliance.

1. Test Process

2. Includes:
Test Planning, Monitoring, Control
Test Analysis
Test Design
Test Implementation
Test Execution
Test Closure Activities
Test Management
Test Documentation and Work products
Test Strategy
Project Rick Management
Test Estimation
Test Metrics
Reviews
Business Value of Testing
Defect Management
Test Process

3.  Test Planning includes:
 identifying activities for meeting objectives defined in test strategy
 identifying methods for gathering and tracking metrics
 determine adherence to plan and assess achievement of objectives
 selection of tools
 scheduling of trainings
 establishing documentation guidelines
 Test Monitoring:
 defining targets
 measuring progress based on test conditions and groups of test conditions
 Test Control:
 is an ongoing activity
 involves comparing actual progress against the plan
 implementing corrective actions when needed
 revisiting test planning activities if needed
Test Planning, Monitoring and Control:

4. Defines “what” is to be tested in the form of test conditions
Test Conditions:
identified by analysis of test basis, test objectives, and product risks.
identified using formal test techniques and general analytical techniques
include:
 Level of testing
 Level of detail and Quality of test basis
 System/Software Complexity
 Project/Product Risk
 Relationship between Test basis – What is to be tested ? How it is to be tested ?
 SDLC in Use
 Test Management tool in Use
 Level at which test design and test work products are to be specified
 Knowledge of Test Analysts
 Level of maturity of test process and Organization
 Availability of project stakeholders
Test Analysis:

5. Test Implementation:
Defines “how” something is to be tested
Identification of test cases
Stepwise elaboration of identified test conditions or test basis using test techniques
Test Design:
Tests are organized and prioritized by Test Analysts
Test designs are implemented as concrete test cases, test procedures, and test data
Involves final checks to ensure test team is ready for test execution. These checks include:
 Availability of required test environment
 Availability of test data
 Delivery of code
 All test cases have been written, reviewed and ready for run
 Test execution schedule
 Order in which manual and automated test cases are to be run
 Check for constraints, risks and priorities

6. Test Closure Activities:
Efficiency is the KEY
begins once test object is delivered and entry criteria to test execution are satisfied
Tools – for test management, defect tracking, test execution and automation – need to be in place
Standards for test logging and defect reporting are published
Tracking of test results
Tracking of test metrics
Metrics to be understood by the team
Evaluating exit criteria and reporting
Test Execution:
Fall into four main groups:
Test completion check
Test artifacts handover
Lessons learned
Archiving results, logs, reports, and work products in Configuration Management Systems

7. Test Strategy:
Secure and utilize resources-people, software, hardware, infrastructure etc.
Carry out value-adding process
Plan and control test process
Understanding testing stakeholders
Alignment of Test activities and Lifecycle activities
Managing Non-functional testing
Managing Experience-based testing
Test Management:
Integration procedures
Test specification techniques
Independence of testing
Mandatory and optional standards
Test environments
Test automation & Test tools
Reusability of software work products and test work products
Confirmation testing and Regression testing
Test control and reporting
Test measurement and Metrics
Defect Management, Roles and Responsibilities & Configuration manager

8. Risk based testing:
Risk Identification:
 Expert Interviews
 Independent Assessments
 Use of risk templates
 Project retrospectives
 Risk workshops
 Brainstorming
 Checklists
 Calling on past experience
Risk Assessment:
 Complexity of technology and teams
 Personnel and training issues
 Conflict within the team
 Contractual problems with suppliers
 Geographically distributed team
 Legacy versus new approaches
 Tools and technology
 Weak managerial or technical leadership
 Time, resource, budget and management pressure
 Lack of earlier quality assurance activities
 High change rates
 High earlier defect rates
 Interfacing and Integration issues
Factors impacting project/product risks:
 Frequency of use of affected feature
 Criticality of feature
 Damage to reputation
 Loss of business
 Potential financial, ecological or social losses or liability
 Civil or criminal legal sanctions
 Loss of license
 Lack of reasonable workarounds
 Visibility of failure leading to negative publicity
 Safety
Risk MitigationRisk Mitigation
GoalGoal
Risk ManagementRisk Management

9. Master Test Plan:
Items to be tested and not to be tested
Quality characteristics to be tested and not to be tested
Testing schedule and budget
Test execution cycle and their relationship to the software plan
Relationships and deliverables among departments
Definition of test items – in-scope and out-of-scope
Specific entry criteria, continuation criteria and exit criteria
Relationships among levels
Test project risks
Overall governance of the testing effort
Responsibilities for executing each of the test levels
Inputs and Outputs from each of the test levels

10. Test Estimation:
Considers all factors that can influence cost, effort and duration of testing activities.
Factors include below:
Required level of quality of the system
Size of system to be tested
Historical data, Industry data and Benchmark data
Process factors:
 Test strategy
 Development and Maintenance cycle
 Process maturity
 Accuracy of project estimate
Material factors
 Test automation and tools
 Test environment
 Test data
 Development environment
 Project documentation
People factors
Complexity of process, technology, organization etc.

11.  Product(quality) risks
 Defects
 Tests
 Coverage
 Confidence
Estimation Techniques: (can be top-down or bottom-up)
 Intuition, guesses or past experience
 Work breakdown structures (WBS)
 Team estimation sessions (e.g. Wide Band Delphi)
 Company standards and Norms
 Percentage of the overall project effort or staffing levels
 Organizational history and metrics
Test Metrics-Definition and Usage:
 Testing Metrics
 Project Metrics
 Product Metrics
 Process Metrics
 People Metrics
Test progress is monitored by:
Definition
Reporting
ValidityTest Manager
Tracking

12. Reviews:
 Contractual reviews
 Requirement reviews
 Top-level design reviews
 Detailed design reviews
 Code reviews
 Test work product reviews
 Test entry reviews
 Acceptance reviews
Types of reviews:
 Informal review
 Walkthrough
 Technical review
 Inspection
 Management reviews
 Audits
Role of review leader:
 Collect review metrics
 Use review metrics to define ROI
 Provide feedback to review participants and stake holders

13. Business Value of testing:
Delivers value to the organization, project, operation in both quantitative and qualitative ways
Distributed, outsourced and insourced testing
Helps manage the application of industry standards
Cost of Quality
Costs of prevention
Costs of detection
Costs of internal failure
Costs of external failure