The ABLUnit Test Runner extension for VSCode integrates ablunit tests into the test explorer.

• Execute ABLUnit tests from the VSCode Test Explorer View
• Display test results in the VSCode Test Results View
• Color coded line coverage highlighting in the editor

This project was developed using the Progress OpenEdge Developers Kit: Classroom Edition. It was primarily tested with 12.2.12, but the unit tests are run for 12.7.0 during the CI builds too.

VSCode is working to improve the testing runner by adding code coverage support. This extension is designed to work with the proposed API and will fully integrate it when officially available. The current implementation mimics some of the proposed functionality where easily possible. For a sneak peak at the new functionality install ablunit-test-runner-insiders.vsix (see releases)vsco into a VSCode Insiders installation. Then, relaunch VSCode with the --enable-proposed-api=kherring.ablunit-test-runner flag.

See VSCode Documentation -> Using Proposed API for more information.

Configuration is optional. Many workspaces will work without any configuration. However, there are advanced options available via the VSCode settings and a test profile configuration file (.vscode/ablunit-test-profile.json).

The settings config allows for a few global options, described in more detail below. This example shows a test file glob pattern and another with a path to a dbconnections .pf file. The ablunit.files.include setting is required for the extension to find tests.

.vscode/settings.json with include and exclude patterns:

{
  "ablunit.files.include": [
    "test/**/*Test.{cls,p}"
  ],
  "ablunit.files.exclude": [
    "src/sandbox/**"
  ]
}

.vscode/settings.json with dbconnections .pf file:

{
  "ablunit.files.include": [
    "test/**/*Test.{cls,p}"
  ],
  "ablunit.params": "-pf path/to/dbconnections.pf"
}

The following table gives a brief description of the available settings via the UI or settings.json files.

The .vscode/ablunit-test-profile.json has additional configuration similar to launch configurations.

A default profile is created when using the ABLUnit: Configure Test Profile command and selecting ABLUnit - Run Tests. This configuration has comments describing the options available.

Note: Only the first test profile will be imported. In the future this extension will allow for multiple entries.

See CONTRIBUTING.md

• npm install
• Make any changes you wish
• npm install -g --save-dev @vscode/vsce"
• npm test or use the Extension Test Runner

• VSCode Marketplace - ABLUnit Test Runner
• Progress Documentation
  • Run test cases from the command prompt
  • Learn About ABLUnit Test Framework
  • ABLUnit Annotations
  • PROFILER system handle
  • Profiler (-profile) startup parameter
• GitHub Repo - progress/ade - OpenEdge Source Files
• Docker Hub - Progress Software Corporation - progresssoftware/prgs-oedb

This is my first VSCode extension, and my first TypeScript project. I am sure there are many ways to improve the code, and I welcome any feedback. I'm also open to collaboration for anyone who might wish to contribute.

Quality code is my passion. Unit testing is an important component of ensuring code remains functional when future changes are made. I hope this extension helps others to embrace TDD and improve their code.