To ensure software quality through extensive coverage requirements, the R.T.M.R tool is based on the previous description of actions around software testing by the actors and process for cities.
It comprises also a repository of requirements and tests repository for multiple projects and multiple versions.
General operating principle of the tool is:
R.T.M.R project correspond to a software to test.
Each version of the software is linked to a version of a R.T.M.R project. These versions are often associated with deliveries occurring between contractor and project owner.
Initially, the administrator of the tool R.T.M.R created a project and its first version. It must assign permissions for different users authorized to act on this new project.
Project managers and analysts feed the repository requirements as and when the code needs.
In collaboration with them, responsible for revenue build test cases associated with this first version and the test campaigns to be implemented by priority level of requirements, requirement types (functional, performance, load ... etc.), the level of risk etc ....
When the new version of the software is delivered, the campaigns of tests are performed to verify the compliance of the software that came with the requirements submitted.
Each action of a test case is associated with a description and an expected result. If during the execution of an action, the result is not consistent, one or more abnormalities may be entered through the module available for this purpose.
The execution of the campaign can generate a comprehensive report containing a summary of results from the execution of scripts and other. This report traces actions with their rate of success and failure.
For each new delivery, an administrator creates a new version of the project. In its initial state, this new version is an exact copy of the previous version, thus including the same requirements and the same test cases.
In the new version, adding, modifying or deleting requirements relating to lot of changes (adding new features, bug fixes, enhancements performance ... etc.), can target testing efforts based on scenarios related and therefore provides coverage of regression testing.