This document describes how to record and run a simple unit test and covers the following topics:

• Before you Begin

• Glossary of Terms

• Creating your First Unit Test

---

Before you Begin

Make sure you have the following:

• License for ApplinX

• Software AG Designer

• Local or remote Natural application to test

See Prerequisites for complete list of system prerequisites.

Glossary of Terms

Assertion

An assertion encapsulates some testable logic specified about a target under test. This can be an attribute-value pair, for example "firstName":"John", or a true-false statment inserted in a program where the developer always expects a certain condition, for example "endOfList":"true". Assertions are stored in the generated JSON file.

Configuration File

Each test project has a configuration file in JSON format. This contains default values for the packages contained in the test project, for example "hostApplication":"my_Mainframe".

Host

The host containing the application you want to test.

Input

Field identified as input field when the path procedure is recorded, for example User ID. Inputs are stored in the generated JSON file.

JSON File

In ApplinX, a JSON file (JavaScript Object Notation) is generated by the Generate Unit Test wizard from the test project. It contains inputs and assertions for the unit test as attribute-value pairs. You can copy a generated JSON file and change the inputs and assertions. The unit test is then run multiple times, once for each JSON file.

Path Procedure

A path procedure corresponds to an individual function, for example LoginFlow or GetUserById. It is the result of the recorded screen flow. From a recorded path procedure you can generate a unit test.

Unit Test

A unit test is generated from a recorded screen flow, for example LoginFlow. A unit test is generated as a path procedure to a new test project or added to an existing test project. The unit test is run from the Java file that is generated in the test project.

Creating your First Unit Test

This section covers the following topics:

• Step 1: Create a New ApplinX Application

• Step 2: Identify Screens and Fields for your Path Procedure

• Step 3: Record your Path Procedure

• Step 4: Generate a Unit Test

• Step 5: Run the Unit Test

Step 1: Create a New ApplinX Application

To create a new ApplinX application

1. From the Software AG Designer, open the ApplinX development environment.

2. Connect to the ApplinX server by double clicking the server icon. A new dialog for credentials is opened.

   

3. In the ApplinX perspective, create a new ApplinX application. Select Local ApplinX server, and from the context menu choose New Application.

   

4. Enter a name for your new project, a description and specify the initialization mode. Press Next. See Application Configuration Parameters in the ApplinX Reference Guide.

5. Under General ApplinX Application Information, specify your Natural host.

Step 2: Identify Screens and Fields for your Path Procedure

To identify screens and fields

• See Screens in the Designing and Developing a Test Case documentation.

Step 3: Record your Path Procedure

To record your path procedure

1. Under the Sessions folder, double-click the Default session to start the green screen host session of the ApplinX application. During this session you record the screen flow of the path procedure.

   

2. Record the screen flow that covers the path procedure.

3. During recording, mark the fields you want to include as inputs for your path procedure.

4. During recording, mark the fields you want to include as assertions for your path procedure.

5. Stop the recording.

6. In the Define Path Procedure Name screen, enter a name, description and folder where the path procedure will be stored.

Step 4: Generate a Unit Test

To generate a unit test

1. Review the path procedure to make sure the inputs and outputs were recorded correctly. You can also edit or add logic to the recorded path procedure to make it more general or specific to suit your needs.

2. Select the path procedure and choose Generate Unit Test.

   

   The following artifacts are generated:

   • Java project that includes a Java file containing the executable path procedure

   • JSON configuration file

   • JSON file containing inputs and assertions

   • required binary files that are included in the Java project

See Working with JSON Files and Managing Test Data under Designing and Developing an Application.

Step 5: Run the Unit Test

To run the unit test

• From the Java perspective, select the generated Java file. From the context menu choose Run as > JUnit Test.