OMrun has an integrated process engine: test steps are grouped into scenarios and carried out manually or via a scheduler.
OMrun can call other tools and programs as main / primary (prior known as "master") or can be called as secondary / replica (prior known as "slave") itself.
The following connections are available, among others:
- UC4 (Automic)
- Tosca Testsuite
- HP Application Lifecycle Management (ALM / QC)
All test cases managed by OMrun can be reused in several scenarios. In this way, highly complex processing and test steps can be automated - we call this approach "scenario of scenario".
OMrun focuses on data as test objects because we at OMIS believe that data structures are more stable than functions. We are convinced that changes to software affect the data and can be detected there. In many cases, there is no need to manually create test data, which reduces maintenance costs.