Search Results

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)...

All testing whether it is at Unit or User Acceptance Testing level is required to be conducted on test environments (non-live). Testing should also be undertaken in an environment that mimics the set- up/configuration of the live system as closely as possible....

Performance Testing checks if the application response is within the range defined by the team in the non-functional requirements. Hence, ensure response parameters are included in the non-functional requirements. Performance testing should capture metrices o...

When considering testing for any Projects or Changes, Test Managers / Test Leads / Team Leaders also need to take into consideration any technical security implications the Project / Change will introduce. Where activities are undertaken within GoR institutio...

Each test should be given one of the following statuses:  Not Started - The test has not started and should be the default status for planned tests at the very start of test execution. Passed - The expected result defined in the test step matches the actua...

At each point of the software development lifecycle, including the go-live, the project team should evaluate the effectiveness of testing. Various techniques, such as trend analysis from live service monitoring, will be used to measure the testing. It is cruci...

Ensure there is a testing representative involved in any planned overall project lessons learnt meetings. Identify and review any areas of improvement that have been raised during the test process (test planning, test design, test execution and test closure...

GoR institutions need to comply with these policies and guidelines of software testing by following the recommendations for each stage of testing. Where it is not possible to follow a particular guideline, the reasons should be clear.  For large projects, the ...

Test control is an activity that runs continuously during the test process to ensure that all planned tests are complete and test results are able to meet the test objectives, strategies and mission.  Test control generally includes the comparison between the ...

This document may be reviewed on daily basis on the corrective, adaptive, perfective or preventive situation as it will be required.

A Requirement Traceability Matrix (RTM) is tool that maps and traces user requirement with test cases. It captures all requirements proposed by the client and requirement traceability in a single document. The main purpose of Requirement Traceability Matrix is...

Software maintenance is carried out after a software product has been launched with the objectives of improving the software, correcting issues or bugs, boosting performance and more. Software maintenance is part of the Software Development Life Cycle (SDLC). ...

Software support is reactive and covers activities to address urgent issues that arise from software use that can hamper software operations or cause downtimes. Software maintenance is proactive and includes scheduled activities to address non-urgent issues or...

This document covers guidelines for support, maintenance, software updates and patch management, software change management and release processes. They apply to all Government institutions in Rwanda.

The following roles are involved in the software support and maintenance process: End users – End users use software systems on a day to day basis. They are responsible for reporting any issues encountered in the software to the support team. End users also...

a)    End users responsibilities Report issues encountered on the software Request for enhancements or improvements in the software based on evolving needs Test changes that are made to confirm they work as expected before they are deployed to the product...

Software support is provided to users after software has been deployed to Production and users have started using it. Support is usually provided  by an internal support team but may also include support from the vendor of the software system if its third part...