The relationship of TestGrip, RRBT and TestFrame
The standard for testing as defined by Logica can be represented schematically as a pyramid. This pyramid covers three test levels: strategic, tactical and operational. The test policy is defined at the strategic level. It’s applied at the tactical level for the management of test projects. At the operational level within these projects, several test levels and types are executed using the test method, test tools and the resources that are defined in the test policy.
A test policy is a translation of the company strategy into instructions forming a measurable
framework for all test activities. It describes standards of the test process, the organisation type
that is used for testing within the company and the relation with Information Technology policy
and quality management. Such an explicitly defined test policy offers a framework for planning and
execution of all test activities. In this way testing ensures that the products fit the company’s goals.
The test project preparation will be completed only once in most cases. It consists of the
following steps:
- Risk analysis & test strategy: This is the main phase of RRB T. The test manager identifies
product risks and their priorities.
- Estimate: The test manager identifies resources that are needed to run the test pro-ject.
- Planning: The test manager identifies timelines for the project. And what needs to be delivered.
- Test organisation: The test manager identifies who will do the testing. Are these people
system developers or people from an internal or external pool of testers? Is testing outsourced
completely?
Download PDF (1.7mb)