Economic vs. Risk based Testing

Risk-based testing is essentially a business risk mitigation process. The focus is therefore on identifying potential software risks, and on evaluating their likelihood of occurrence and degree of impact. This risk evaluation is then used to prioritize the execution of tests, with a key goal being to minimize the number of test cases – and therefore the time and cost required for testing.

Economic testing is a fundamentally different approach, as it is a “success enabling process.” Thus, the focus is not on potential problems, but instead on potentials for success. The following analogy should help illustrate the difference:


Companies that do not have a dedicated team of software test specialists often assign staff from the helpdesk, development or business domains to perform testing. Though well versed in technical and business knowledge, these individuals often lack specific software testing know-how. This workshop has been specifically designed for them. The workshop provides an introduction to systematic software testing for individuals who document and execute test cases as a side duty. A key objective is to highlight the contribution of software testing to added value in the various software development stages: from code and unit testing to component tests, and through to integration, system and acceptance testing.

SAP Test Consulting

In many companies, SAP solutions represent the backbone of IT systems, for they are often used to control critical business processes. As a result, interface development and adaptations to meet the needs of customers involve significant complexity.
Comprehensive testing is therefore a must for the new installation of a SAP solution, but also for system upgrades and support or enhancement packages. Due to their broad range of functionality, SAP solutions typically lead to large testing volumes and, in turn, high costs: The IT and business departments must each test the entire system with all relevant use cases.

Our 3-phase concept has proven to be a particularly viable approach for SAP testing. Use cases are recorded and prioritized, and the test cases are then generated and parameterized from the use cases. This approach is especially reliable and cost-effective with a view to test automation.