Software Testing and Quality Assurance Guidelines
These software testing and quality assurance guidelines aim at guiding and addressing concerns on software quality processes during the acquisition, development, and maintenance of systems by developers, managers, and quality assurance teams.
Introduction
These software testing and quality assurance guidelines aim at guiding and addressing concerns on...
Purpose of the document
This document is divided into two sections and describes the two key elements to the approach and...
Overview
RISA is driving the government’s digitalization and innovation plan by supporting sectors and ins...
Scope
This document provides policies and guidelines for the planning and execution of software testing...
Software Testing Policy
Purpose of this Software Testing policy
The testing policy outlines the high-level strategy and principles for software testing. It outli...
Mission Statement
To ensure that any changes to software do not jeopardize the quality characteristics of mission-c...
Software Testing Policy Objectives and Principles
The following are the main objectives of the software testing policy: To ensure that testing i...
Benefits of the Software Testing Policy
This testing policy aims to give the GoR institutions the observable advantages listed below: ...
Testing Guidelines
Purpose of Software Testing Guidelines
The major purpose of these software guidelines is to provide a set of recommendations and best pr...
Definition of Testing
Below is a description of how testing is defined generally. General Definition Testing is the p...
Risk Based Approach to Testing
All facets of the testing lifecycle should be approached using a risk-based approach. Testing sho...
Software Testing Guidelines Objectives
The key principles that should guide the development of strategies for all testing activities are...
Roles and Responsibilities
The table below describes the three aspects of roles and responsibilities of personnel that are t...
Fundamental Test Planning Process and Strategies
The four stages of the Fundamental Testing Process must be completed in the correct order. These ...
Approaches to Manual Testing
Manual testing is an essential part of the testing approach, given the volume and diversity of th...
Approaches to Automated Testing
The focus of these guidelines and the initial remit of GoR institution Testing Services is aimed ...
Defect Management
The way in which defects are handled is arguably equally as important as running the tests themse...
Test Data Management
Purpose of the Test Data document
A test data document should be developed as part of the testing process. The purpose of the test ...
Ways of Collecting Test Data
Test data can be collected in different ways: 1) Automated2) Manual3) Data copying4) ...
Practical guideline on how to use test data
1) Use all combinations of valid and invalid data when testing2) Collect data using positiv...
Test Environment Management
All testing whether it is at Unit or User Acceptance Testing level is required to be conducted on...
Performance and Security testing
Test status and reporting
Following the successful completion of agreed test cases, the test lead, test manager and project...
Statuses
Each test should be given one of the following statuses: Not Started - The test has not start...
Evaluation of test processes and test improvement (Continuous Improvement)
At each point of the software development lifecycle, including the go-live, the project team shou...
Project Lesson Learned workshops
Ensure there is a testing representative involved in any planned overall project lessons learnt...
Compliance and Audit
GoR institutions need to comply with these policies and guidelines of software testing by followi...
Test control and review history
Requirement and Traceability Matrix
A Requirement Traceability Matrix (RTM) is tool that maps and traces user requirement with test c...