Building and executing unit tests is an essential part of OpenEdge development, but managing large test suites, handling execution results, and configuring the testing environment can sometimes make the process more complicated than it needs to be.
ABLUnit Runner is a Visual Studio Code extension designed to make ABLUnit testing simple and easy to use and more accessible by integrating test execution and result management directly into the VSCode.
The extension executes a batch script (Windows) / sh script (Linux) to initiate ABLUnit test runs, processes the generated results, and imports them into the native VS Code Test Results and Test Explorer views. This allows developers to re-run specific tests, test suites or failing tests, inspect failures, and quickly navigate to the relevant test code without leaving their development environment.
Whether you’re running a single test case or an extensive test suite, ABLUnit Runner provides a streamlined testing experience.
Seamless Integration with Existing OpenEdge Projects
One of the main goals of ABLUnit Runner is to work with existing OpenEdge projects without requiring developers to manually recreate their configurations.
The extension automatically detects and reads configuration files from two commonly used development environments:
Progress Developer Studio for OpenEdge
For existing Developer Studio workspaces, ABLUnit Runner reads:
- DLC environment variable
- .propath – to determine the project’s PROPATH.
- databaseConnection.xml – to discover available database connections.
- .dbconnection – to identify the database connections relevant to the project.
This allows developers to bring existing Developer Studio projects into VS Code and start running tests without additional configuration.
Riverside Software OpenEdge ABL Extension
For workspaces using the Riverside Software OpenEdge ABL Extension, ABLUnit Runner automatically reads the openedge-project.json configuration file and uses the existing project settings.
Supporting both environments makes it easier to adopt VS Code for OpenEdge development while keeping existing project configurations intact.
A Better Testing Experience in VS Code
ABLUnit Runner integrates directly with the VS Code Testing interface, making it easier to execute tests and investigate failures.
Some of the key capabilities include:
- Test Explorer Integration: Run ABLUnit tests and view execution results directly in VS Code Test Results view and Test Explorer view.
- Rerun Test, Rerun Suite, Rerun Failed Tests: Quickly rerun individual tests, parent test suite or all failing tests from the Test Explorer and Test Results context menus.
- Error Navigation: Failed tests are highlighted at the corresponding source code line whenever the information is available. If an exact line cannot be identified, the extension falls back to the test method declaration.
- Execution Status: A status bar animation indicates when an ABLUnit session is running, while also displaying the Process ID (PID) of the current session. For whatever reason if needed, the process can be stopped right away by clicking the ABLUnit Status status bar and confirming a short question
- Fresh Test Results: Previous execution results and logs are cleared before each new run, preventing outdated results from appearing in the Testing view.
These features make it easier to monitor test execution, identify failures, and navigate directly to the code that needs attention.
Built for Small and Large Test Suites
Not all testing scenarios are the same. Sometimes you only need to run one test case, while other times you need to execute hundreds or thousands of tests.
ABLUnit Runner is optimized for long-running operations and large-scale test suites, but it works just as well for smaller projects and individual test cases.
By using an OpenEdge batch execution process and integrating the results into VS Code, the extension provides a consistent approach regardless of the size of the test suite.
What’s Next for ABLUnit Runner?
ABLUnit Runner has continued to evolve, with several additional capabilities already implemented to make the testing experience even more flexible and reliable.
These include:
- Linux Support: Extending the extension to Linux environments.
- Test Session Management: Stop or cancel running test sessions through the status bar or VS Code’s native Testing Stop button, with protection against overlapping executions.
- Rerun Failed Tests: Execute all failed test cases in a single OpenEdge batch session and update the existing results.
- Custom OpenEdge Profiles: Support for .vscode/profile.json, including configuration overrides, recursive profile inheritance, and fallback to default project settings.
- Multiple Test File Execution: Run tests from multiple .cls and .p files, folders, or mixed selections directly from the VS Code Explorer, using a single OpenEdge batch session.
These features introduce additional flexibility and control, especially when working with larger and more complex OpenEdge projects.
In an upcoming article, we’ll take a closer look at these new capabilities, explore how they work, and show how they can further improve the ABLUnit testing workflow in VS Code.
Author: Corina Man, Developer
Corina is one of those people every team relies on. She’s committed, dependable, and always ready to jump in and help a colleague no matter the challenge. Her positive energy and sense of fun make even the busiest days feel lighter, and she brings that same spirit into everything she does. Outside of work, Corina is a proud mom to two adorable girls and a passionate reader who’s rarely without a good book. Whether she’s supporting her team or getting lost in a story, she brings care, consistency, and a genuine love for what she does.



