Contact
FINARIS
Financial Software Partner GmbH
Sömmerringstraße 23
60322 Frankfurt am Main
+49(0)69 254 98 - 0
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
Test process
Alternative Testing Scenarios
Basically, there are three different infrastructural approaches for testing:
- No testing infrastructure, so called "ad hoc"-testing
- Specific testing environment, optimized for a specific testing domain
- Using a general testing environment (commercial solution or own development)
RapidRep Test Suite can be applied to all three testing scenarios!
Ad Hoc Testing
The focus of this testing approach is mainly the spontaneous execution and analyzation of few test cases. In this form, the planning and controlling of testing activities is less important.
RapidRep supports this approach very efficiently, since the RapidRep Test Runner application provides a comfortable testing user-interface that allows a fast and easy creation of test cases that can be executed repeatedly. The custom views grant an organized visualisation of all test activities.
Specific Test Environment & general Test Environment
Specific and general test environments are used in order to link test cases with requirements and to afterwards organize them into test plans. Deviations from expected results are stored as defects seperately.
When using test environments, the main focus is put on the efficiency of the overall test process. Special reports show the current progress of testing and illustrate test coverage and failure rates of test objects.In order to support popular test management and defect management system, RapidRep provides specific connectors. In-house developments can be applied as well, if they fulfil some minor requirements.
The interaction between Test Management and Test Execution
In the left part of the figure, those components are shown that are particularly often used in major projects for test management. At first, all requirements that are to be tested are captured and assigned to a test plan.
A test plan is used to define which test cases are needed for testing a requirement. The rest cases are then executed by calling a script. The results from the test case execution (passed or failed) are then reported back to the test plan. In case of a deviation between calculated and expected results, an entry is created in the defect manager containing details allowing business analysts and developers to determine the root cause of the failure and to fix it.
The right part of the figure shows the most important but also most difficult part of the test cycle - the actual test execution. At this place, the question is answered whether the calculated results are consistent with expected results and if a migration has been performed successful or not.