Introduction

In this entry we explain, how you can integrate the ABLUnit testing framework into Build.One development processes. With the ABLUnit testing framework developers are able to write and execute ABLUnit tests for their written custom code. This means of course, that written code must be testable.

How-to: ABLUnit with Build.One

• In Build.One developers are able to use the ABLUnit testing framework from progress, which is documented here: https://docs.progress.com/bundle/openedge-developer-studio-olh-117/page/Overview-of-ABLUnit-testing-framework.html
• All necessary references are already available in the propath of the framework and useable

Execute ABLUnit Tests

• There are two ways to execute them:
• Execute them directly in gitpod: This can be done by executing manually the test files and checking result or by include the tests into a CLI command and execute this one
• Execute them in the CircleCi build process: Therefore you need some CLI executable tests and than can add these in .circleCi/config.yml to be executed in CircleCi workflows.
💡
This may lead to commit wrong code, since the tests will be executed after committing. So not the recommended approach

Back to Documentation

Back to Home Page