Search Results

i.    Map Design Principles: Simplicity - Maps should be visually clean, focusing on the most important information while removing unnecessary elements. Legibility - Ensure that the map's text, labels, and symbols are easy to read and understand, even when...

This document is divided into two sections and describes the two key elements to the approach and vision of testing within the GoR Institutions: Software Testing Policy: An overview of the values supporting the testing approach Test Guidelines: These are b...

RISA is driving the government’s digitalization and innovation plan by supporting sectors and institutions in their automation journey. Automation of services and processes involves acquiring or developing software. In order to ensure that the software meets ...

This document provides policies and guidelines for the planning and execution of software testing activities for Government of Rwanda Institutions. It is crucial that the consumers of this document (i.e., software project teams in Government of Rwanda Institut...

The testing policy outlines the high-level strategy and principles for software testing. It outlines the test goals and objectives, benefits and strategies for test process improvement. All subsequent test strategies and low-level test plans will be establishe...

To ensure that any changes to software do not jeopardize the quality characteristics of mission-critical systems used by GoR Institutions. To verify, validate, and evaluate the quality of software or systems being delivered and to ensure that testing is perfo...

The following are the main objectives of the software testing policy: To ensure that testing is planned early in the project so that testing activities may be started as soon as possible in the project life cycle, and resources planned accordingly. To iden...

This testing policy aims to give the GoR institutions the observable advantages listed below: Ensures that testing is a standardized and repeatable activity rather than a customized activity for each project or software modification, i.e., that we are not r...

The major purpose of these software guidelines is to provide a set of recommendations and best practices for ensuring that systems are properly tested to achieve high quality software solutions. These guidelines explain the basic framework of the testing proce...

Below is a description of how testing is defined generally. General Definition Testing is the process of executing program(s) with the intent of finding errors, rather than (a misconception) showing the correct functioning of the program(s).  The difference ...

All facets of the testing lifecycle should be approached using a risk-based approach. Testing should always be done with a view to identifying and reducing any risks the Project/Change may present, depending on the project objectives. The necessary testing wil...

The key principles that should guide the development of strategies for all testing activities are described in the following testing objectives: To ensure creation of a testing plan early on in the project so that resources may be allocated appropriately, a...

The table below describes the three aspects of roles and responsibilities of personnel that are typically required to be involved with testing for software. The following defines the three aspects: Standard Testing Roles This is an industry standard testing ...

The four stages of the Fundamental Testing Process must be completed in the correct order. These are Test planning, Test Design, Test Execution and Test Closure. These stages should be carried out in this logical order for any Test Level i.e Unit, System, Syst...

Manual testing is an essential part of the testing approach, given the volume and diversity of the applications that will be developed, supported and utilized by GoR. There are three test techniques to undertake manual testing which have been detailed below. ...

The focus of these guidelines and the initial remit of GoR institution Testing Services is aimed at introducing and embedding the key principles of manual testing to GoR Institutions and associated business areas. Once the principles and associated processes o...

The way in which defects are handled is arguably equally as important as running the tests themselves. The basic process of defect management is described below and should be followed whenever there is a test phase being undertaken. Step 1: Defect observed ...

A test data document should be developed as part of the testing process. The purpose of the test data document is to help programmers identify coding errors during the initial stages of a project. This allows them to make changes and submit for further testing...

Test data can be collected in different ways: 1)    Automated2)    Manual3)    Data copying4)    Back-end data injection5)    Slicing

1)    Use all combinations of valid and invalid data when testing2)    Collect data using positive and negative testing.3)    Give yourself ample time to test data.4)    Reevaluate data during each phase.5)    Involve multiple team members in the collection.6)...