A guestpost by Sebastian Weha.

You probably know the Software Development Lifecycle (SDLC). It describes the process from requirements analysis to a finished software and its evaluation. To implement the SDLC, there are many methods (and lots of discussion about which of them is best): agile software development, the waterfall principle, DevOps, ….

But there’s one thing, all of them have in common: testing the software is crucial.

So of course, this also applies to the Automic development — at least in theory. In practice, however, testing is often neglected.

I made this experience in many projects. That’s why I came up with the idea of automating the testing process and providing a solution for it in best4Automic (b4A).

The solution is based on b4A packages, which are based on the structure of Automic Action Packs. In the default configuration, it uses the structure of the action packs so that customers who already use action packs can start immediately.

In test specifications, you define which tests are to be carried out.

What does a Test Specification Look Like?

The tests are described in Cucumber and the Gherkin syntax.

Basically, the tests are structured as follows:

  • Feature: Describes a set of test cases (scenarios) that are thematically related
  • Scenario: Describes a single test case
  • Given: Describes the steps to be checked before the actual test execution (preconditions)
  • When: Describes the actual test execution
  • Then: Describes the steps to be checked after the test execution (post-conditions)

The structure of specification in Cucumber/Gherkin.


To illustrate this with an example, I have created a simple workflow. This consists of a PromptSet for text input and a script that returns the input.

We test this workflow with the following test specification.

Feature: Test the package for Philipp Elmer blog post!
	Scenario: Test Script and check if input is contained in report
			|Key				|Value			|
			|INPUT#				|Test Input	|

			|Task									|status		|

The specification contains a feature with a very simple scenario.

First of all, we check with GIVEN whether all three objects exist in the client. If one does not exist, the test aborts.

The WHEN section describes the execution of the workflow and passes the PromptSet parameters. The table shows the PromptSet parameters that are passed (Key: INPUT#, Value: Test Input).

THEN checks if the task in the workflow has the status ENDED_OK and if the report contains the entered text.

Of course, we could also test other scenarios, like other inputs. However, this is not necessary for our example.

How to run a test specification

The Gherkin syntax runs tests on the Cucumber framework and retrieves the results from there. This step is not trivial, as we need an interpreter that translates Automic into the expected results and into a language that Cucumber understands.

We implemented this as the module ta.Execute in the best4Automic Solution.


For administrative tasks and projects, extensive manual activities on the ONE Automation Platform are necessary: mass changes, clean-up tasks, time-consuming analyzes, or daily doing. The best4Atomic Solution (b4A) offers a comprehensive set of modules that extend the functionality of your ONE Automation platform, simplifying the work and eliminating manual errors (especially in mass changes).


With the module, test cases specified in Gherkin can be executed. You can either pass the test definition in a text file or store the test definition in a DOCU object. In this case, I specified the DOCU object. It also stores the test results of the last run.

In this configuration window, you can choose where the module gets the test specification and how the report should be output.

After running the test, you get a report with the results.

You can also find this report in the object that you specified for the report. This allows you to analyze and process the test results using Automic scripting tools. For example, you can forward the test results as an e-mail or transfer them to your test management software.

Running the test was successful and the text “test input” was found in the SCRI activation report.

The example here is of course very simplified. Usually you have to test significantly more scenarios. But they all work the same way I described here.

Do you have your own ideas for testing your Automic workflows? Then get started on the implementation.

Sebastian Weha

Automic Expert and b4A Developer

Sebastian is a certified Automic Expert and b4A Developer. With great passion he meshes Automic with other products, controls them with Automic, and simplifies and automates workflows. He spends his free time with his family and traveling to new places in the world.

best-blu — Consulting with Energy

best-blu specializes in the automation of business processes of large and medium-sized companies. With approximately 35 employees, they work in the four core areas of digitalization: Business Process Automation, Business Process Management, Software Development and ERP Processes (SAP). As a Premium Service Partner of Automic, with the excellence initiative bestXperts and, of course, through successful automation projects at well-known companies, they have made a name for themselves as a specialist for automation and digitalization of business processes.

Get concentrated knowledge from 5 years of AutomicBlog

Download an archive with all old articles:

  • Features, SQL-Tricks, and handy Scripts.
  • 63 extensive articles (+ comments).
  • Used by Automic experts around the world.

Subscribe to the newsletter and immediately get all articles!

[caldera_form id="CF572741b60f87f"]