Our phase model shows a flowchart for the successive development of an efficient use of customer-specific test automation. The procedure takes the original customer goal into account:
- Use of test automation as a service (TAaaS)
- Establishment and expansion as in-house TA competence centre (CC)
To make the recurring test efforts more efficient, Mentopolis offers with "Keep IT Green" an eggplant-based test portfolio that is easily extendable and can be tailored to business requirements.
After the basic proof of feasibility in the PoC, we split the procedure into practical phases in order to meet the defined requirements.
On the one hand, focus is placed on the transfer of knowhow to enable independent realization and, on the other hand, priority is given to the direct implementation of externally defined test automation.
The eggplant technology and the Mentopolis KIG architecture allow the Test Automation infrastructure to be mapped in accordance with explicit customer requirements.
The technical design provides the basis for a clear allocation of all TA project planning tasks between the customer and Mentopolis.
Organizational and administrative activities are to be evaluated independently of in-house governance and security requirements and, as a basic principle, allow two technological implementation variants.
The non-invasive approach of the eggplant basic technology and the KIG Suite (methods & solutions) enable us to offer our customers a real "Test Automation-as-a-Service".
The customer determines the systems to be tested, the relevant business applications and names workflows or use cases.
We specify the corresponding test cases, develop the EEP test scripts and configure YOUR KIG system for operation. This means that development and operation can be freely scaled at any time.
We only need remote access (VNC, RDP) to the GUI of the test objects. No relevant SW installations. No consultant teams on site at the customer.
Just real "Test Automation-as-a-Service".
Real means: customers submit their test requirements and get back the finished results for the defined test objects. They determine the frequency of execution.
Real means: the customer determines where our test laboratory is located - whether in the customer cloud, on-premise or in our cloud.