TA Studio

The management and control instance of our "Keep IT Green" solutions

TA Studio

TA Studio includes purpose-specific, methodical extensions of eggplant functionality (e.g. enhanced programming and parameter management). This method represents a functional extension of native eggplant scripting and leads to high reusability and variability of the test scripts.

Core elements of TA Studio are a relational database as repository and a GUI (TA Studio interface) that communicate with the eggplant modules (see figure).

Performance characteristics

Project management

  • A project organization incl. audit security via KIG repository
  • Controlled TA execution in the eggplant universe
  • Project reporting and statistics

Enhanced Eggplant Programming

  • KIG parameter management (control and configuration module)
  • EEP (Enhanced Eggplant Programming) as programming extension
  • EEP libraries for direct integration into eggplant scripting

Module

TA Studio provides an administration interface that can be used to call available test administration objects and adjust the test execution configuration. User administration allows all participants to be assigned to their projects. Different tests can be created and configured in each project. All project-relevant information can be edited in a dedicated area and adapted to current requirements.

"Enhanced Programming" libraries are extensions and simplifications for scripting with eggplant that can be used many times. In addition to already implemented standard functionalities, scripts are provided with "parameter handling" in order to map complex operations and tests that accelerate and improve the creation of tests.

In order to be able to establish the assignment between tests performed and system information of the SUT (system under test), relevant hardware and software information on a test machine (SUT) is obtained in TA Studio. This data allows a dedicated release of terminal devices with specified hardware and software configuration. The test results and their associated SUT data are available for auditing.

Parameter managmend maximizes the flexibility of test execution and also adaptation to the test environment and infrastructure of the customers. In this module all relevant parameters can be edited, added and removed.

The KIG Repository is the backbone of TA Studio. It is based on a relational database in which the relevant information from test parameters and test results to the hardware and software information of all test clients (SUT) is managed. The KIG Repository provides data for the tests and is the basis for reports, statistics and analyses in the area of evaluations.

In order to clearly separate projects and test sets, TA Studio contains a corresponding administration interface and the user administration contained in it allows all participants to be assigned to their projects. Different test sets can be created and configured in each project. All project-relevant information can be edited in a dedicated area and adapted to current needs.

Repository database

All information managed and/or generated by TA-Studio is stored in a commercially available relational database, ensuring reliable and versatile data storage.

Test definitions

The repository contains all information about your test cases in a hierarchical order.

The object to be tested. In workplace administration, this is an "application version" that is to be used at the workstations. This makes it possible to assign an "application" from the application databases. However, it can be any software unit to be tested - define it according to your requirements.

Each test subject can be divided into several modules. This is especially useful for larger test subjects such as large applications or application suites (e.g. Office 365 should be divided into Word, Excel, etc. modules). For small test subjects, a single test module may be sufficient. A single parameter set can be provided for each test module (see next section).

Any number of test cases can be defined for each module. Each test case corresponds to a script in eggplant (you can use one script for multiple test cases). A test case can consist of a single atomic test step (as used in eggplant's DAI module) or a complete workflow with many test steps, as needed.

Any number of parameter sets can be defined for each test case. These parameters are the values of input fields or list selection options, etc., as well as the expected result values needed to perform a test and verify the results. During a test run, each test case is executed one parameter set at a time as defined in the test scenario (see below). Configuring multiple test sets with the same parameters but different values allows you to use one script to run with different data constellations.

In contrast to the points described above, the test scenario is created by the TAS analyst. A test scenario defines a test run. The analyst adds or removes complete test building blocks and/or individual test cases from the scenario and selects the appropriate parameter groups for the test case. When executed, all test cases added to the scenario are executed one after the other. All scheduling functions provided by the Eggplant Manager are available for the configuration of the scenario plan.

One of the main advantages of TA Studio is that it allows the use of parameterized test scripts in a simple way. The parameters are entered and managed using the forms provided by TA Studio. The scripts access these parameters using methods provided in the Sensetalk EEP library included in the TA Studio suite.

While the parameter sets are created by the TAS Engineer, they can be modified or extended by the TAS Analyst, e.g. to add or change input parameters for a created test case, since no scripting knowledge is required.

The parameters are used on three levels.

Global parameters that only depend on the test environment (e.g. file paths, TA database name, etc.) only need to be configured once.

Module parameters: parameters can be configured for each test module. These are only the module-dependent parameters (access paths, labels, etc.) and are the same for all test cases of this module. This is a very powerful option, e.g. the use of "XPATH parameters" for selenium in the white box test, which greatly reduces the maintenance effort for test scripts, while the application is still subject to several changes.

As described above, the test case parameters for each test case are unique and essentially contain the input and output data to use/expect when performing the test. The ability to create multiple parameter sets for each test case makes it possible to run the same script with different data constellations. In this way, test coverage can be significantly increased with minimal effort.

Enhanced Eggplant Programming (EEP)

Our methods tool box for KIG programming

KIG methods allow development with "Enhanced Eggplant Programming" (EEP)

Only the KIG TA Suite allows the implementation of a "globally unique" technology based on eggplant components: EEP.

The eggplant system is controlled, parameterized and the classic EP scripting functionally extended via libraries. On this basis, a highly flexible method can be used in TA development that enables a use case to be deployed via EEP as a maximum variable mapping in the transformation to a test case.

In addition to the library, the system includes a central repository for audit-proof historization of all test runs performed. At the same time, parameter management and the evaluation of the test runs in TA Studio are transparently available for the engineer, the tester and the project manager.

Enhanced Eggplant Programming offers significant advantages

  • Maintainability of EP scripts
  • Reusability of test runs
  • Use of modular script design
  • Parameter application and control
  • Management and implementtaion the parameter model
  • Integration of EEP library (simplification of complex functions)
  • Creation and management of test data

Enhanced Programming Libraries

The Enhanced Programming libraries are extensions and simplifications for scripting with eggplant that can be used many times over. In addition to already implemented standard functionalities, scripts are provided with "parameter handling" in order to map complex operations and tests that accelerate and improve the creation of tests.

KIG workflow

Workflow of a KIG analyst

The analyst creates a test scenario in the project, defining the modules, the parameter sets and the SUTs. He can then select whether to start the test run immediately or run it overnight or on weekends, for example. At the end of each test run he can then view the results in detail.

Workflow of a KIG engineer (development)

Implementing a test

A project is created or edited. The engineer creates the subject test, creates the module and the module parameters, describes the script name, develops the module script, creates the test case, describes the script name, develops the test case script and creates the parameter sets and the parameters.

Architectural model

The TA Studio (as administration and control unit) represents the central coordination instance between the eggplant-based development platform (incl. EEP libraries) and the administrative test activities, thus allowing both the parameter-supported configuration of the TA scripts and the variable handling of the execution procedures.

The entire KIG suite (with TA Studio as GUI, KIG repository as RDBMS) thus provides a methodologically unique and highly efficient procedure in the TA development and test laboratory. Existing test scripts of common procedures can be integrated.

Download Flyer

TA Studio

TA Studio

Flyer, Deutsch

Download PDF — 2 MB
TA Studio

TA Studio

Flyer, Englisch

Download PDF — 2 MB

Sound interesting?

Let`s talk! We will be happy to advise you.

Close
Jump to top