Our TA suite Keep IT Green (KIG) manages the complete TA lifecycle (development, administration and control) in operations and delivers ready-made testsets (pre-assembled and parameterizable) as well as TA methods (exclusive KIG libraries and high-performance EEP programming) to increase TA productivity, facilitate maintainability, and enable high reuse adaptively.
- The connectors included in TA Studio enable the central control of various (external) test engines / systems, robotic solutions and MS Office (VBA, VSTO as well as via add-in technology). Due to the open architecture, connectors to other systems can be easily implemented.
- Interfaces enable the control of TA-Studio from external systems, as well as the feedback of test results to monitoring systems.
- The included reporting services allow flexible evaluation of all test results and data.
The complete TA lifecycle (project and operation) is mapped centrally with TA Studio (GUI)
Analyses and reporting are available in the KIG repository in a audit-compliant form
Use case specification and test case design are methods-based
Test scripts are created efficiently using EEP (Enhanced Eggplant Programing)
Easy maintainability and reuse through KIG libraries and best practices
Jumpstart with out-of-the-box workplace test sets (configurable and adaptable for WP test areas)
The core processes in test automation: specification & development as well as operation & analysis/reporting
The KIG components provide each sub-process in the test automation with method-secured solutions, and the TA workflow (Spec - Dev - Ops) delivers well-founded analyses as well as multi-stage reporting results. All data arestored centrally in the KIG repository (RDBMS) in an audit-compliant manner.
Keep It Green has no restrictions regarding the systems, platforms, devices or development languages to be tested. The non-invasive approach communicates from the test client (SUT) exclusively like a "shadow user" - no interventions in the system or applications are necessary for the test execution.
The test client (SUT) itself, which is connected to the corporate infrastructure, is controlled by us only and exclusively via KVM, VNC or RDP, i.e. we do NOT need any additional communication components or protocols within the SUT or beyond.
Within your enterprise infrastructure, the test client (SUT) operates ONLY with the available protocols already released in-house.
The protocols VNC and RDP used by us exclusively concern the communication between the TA components in the test laboratory and allow a control of the test clients (SUTs).