Test-Editor is a lightweight application for specifying, implementing, and executing user acceptance tests, that lives in your browser. This page provides a high-level overview of its user interface and its central components. If you would rather like to jump right in and try out Test-Editor for yourself, have a look at one of the quickstart tutorials. If any questions should arise, you may want to come back here to get your bearings by looking at the overview, or look up individual terms in the glossary further down.

Overview

Overview

In the screenshot above you can see the different areas of Test-Editor-Web, indicated in yellow. In the following, each area is briefly described.

1. Test Navigator

In this area you can specify the structure of the different test artifacts. You can create, delete, rename, cut, copy, and paste test artifacts and refresh the workspace. In addition you can filter the different test-artifacts, so that just the specific test-artifact is visible which was selected.

2. Editor Area

This area is the place to write different test artifacts. The editor supports you with a content completion of the different possibilities during typing and saving your test case, e.g. through the shortcut CTRL + S.

3. Test Step Selector

The Test Step Selector provides you with an overview of the test steps available for defining test cases.

4. Test Execution Navigator

Here you can execute the chosen test case by clicking the start button on the top left corner of this area. After test execution, the results of the individual test steps are indicated by either green (success) or red (failure) icons. In the latter case, details regarding the cause of the failure can be inspected in the Test Execution Details.

5. Test Execution Details

In this area, details about the test step selected in the Test Execution Navigator are shown. In case of failures during execution, this area offers hints about what went wrong. The general sequence of events during test execution can be traced by accessing logs and inspecting screenshots.

Glossary

Application Mapping
A set of platform- or application-specific test steps, mapped to concrete actions to be performed for testing, that are implemented in test fixtures.
Application Mapping Language (AML)
A language used by testers to define the platform- or application-specific vocabulary for the test steps, and by developers to map these steps to the concrete actions to be performed for testing, implemented in test fixtures.
Component
A component is a container for UI elements and interactions. In case of a web application it could be used to describe a single web page.
Developer
A person who is involved in the development of the software under test. User acceptance tests described with the test case language (TCL) are continuously executed during the development process to check the progress with each development increment, and to validate the implementation.
Domain Expert
A user of the software under test, or other stakeholder, who has a deep understanding of the problem domain. Domain experts specify what they expect the system to do and how it should behave, using the test specification language (TSL).
Locator Strategy
Locating elements on the UI is described using locator types (for further information on locating web elements view this Selenium documentation). The web-fixture allows to choose locator types for web applications. Available locator types allow locating by XPATH, name, identifier, link text, CSS (for further information see W3Schools CSS Tutorial) or XPath (for further information see W3Schools XPath Tutorial).
Software Under Test (SUT)
The software system for which user acceptance tests are created by testers. It is (going to be) used by domain experts, and implemented and maintained by developers.
Specification Step
A single step taken as part of a task to be performed with the software under test. Sequences of specification steps can form test specifications.
Test Artifact
A file used by and / or created with the Test-Editor-Web for the overall purpose of user acceptance testing. In particular, these include files containing test specifications, test cases, and application mappings test case language (TCL).
Test Case
A user acceptance test defined in terms of a sequence of test steps to be executed, and expressed using the test case language (TCL).
Test Case Language (TCL)
A language used by testers to implement test cases conforming to test specifications, by defining the necessary, concrete test steps for automatic execution. See this tutorial to learn about writing test cases with TCL.
Test-Editor
An application dedicated to automate the tip of the testing pyramid—acceptance testing—to enable automated product releases and provide confidence in reliable product operation. Designed to bridge the gap between domain experts, testers, and developers, Test-Editor is a modern application that integrates well with container technologies. See Overview for a description of its user interface components and functions, and Tutorials to learn about using it.
Test Fixture
A software library that implements concrete actions, specific to the platform and technology stack of a given software under test, to be performed during test execution. Developers use application mappings to bind test-steps to fixture logic. Out of the box, Test-Editor comes with fixtures that enable the testing of web applications, in particular Angular applications, REST services, Java Swing applications, and mainframe applications through 3270 terminal emulation.
Test Specification
A usage scenario describing an interaction with the software under test, written by domain experts to express desired system behaviors in a testable manner.
Test Specification Language (TSL)
A language used by domain experts to write test specifications of desired system behaviors. Testers refer to TSL artifacts when implementing them as test cases, using the test case language. See this tutorial to learn about writing test specifications with TSL.
Test Step
A single, automatable step taken as part of a test executed against the software under test. In test cases conforming to test specifications, each specification step may be implemented by arbitrarily many test steps.
Tester
A person responsible for user acceptance testing against the software under test. Testers write executable test cases using the test case language to implement test specifications.