ABLUnit Test Runner 🏃‍♂️🏃🏃‍♀️

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

🌴 Features

Execute/Debug ABLUnit tests from the VSCode Test Explorer View
Display test results in the VSCode Test Results View
- View code coverage in VSCode
Debug Listing Preview editor synced with source code

📷 Code Coverage Screenshot

code coverage example screenshot

🐞 Debug Listing Preview

Debug Listing Preview screenshot

📝 Supported OpenEdge Versions

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

⛺ Configuration

Configuration is optional. Many workspaces will work without any configuration. However, there are advanced options available via the VSCode settings and test profile configuration.

📐 Settings Configuration

The settings config allows for a few global options, described in more detail below. This example shows a test file glob pattern.

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

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

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

Setting	Default	Description
`ablunit.discoverAllTestsOnActivate`	`true`	Search all workspace files for tests on extension activation. It may be beneficial to disable this for large workspaces, in which case the extension will find tests as files are accessed.
`ablunit.debug.hide`	`false`	Hide debug tests run button in the test explorer view. Extension must be reloaded for this setting to take effect.
`ablunit.files.include`	`[ "*/.{cls,p}" ]`	Glob pattern array matching test files.
`ablunit.files.exclude`	`[ "/.builder/", "/.pct/ ]`	Glob pattern array to exclude test files.
`ablunit.test.classlabel`	`classname`	The label format for test classes. Example for class with path `com/example/myClass.cls`: class-type-name example: `com.example.myClass` filename example: `myClass.cls`

🧪 Test Profile Configuration

Access the test profile configuration in vscode via the Test: Configure Test Profiles command. Test profile configuration is stored in .vscode/ablunit-test-profile.json. Configuration details are available via JSON schema/intellisense and can be found in the sample file ./resources/ablunit-test-profile.detail.jsonc.

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

Note: The configuration is an array but only the first test profile will be imported. In the future this extension may allow for multiple entries. If you have suggestions for use cases please reach out via GitHub issues.

👷‍♂️ Contributing

See CONTRIBUTING.md

💻 Development

npm install
Make any changes you wish
npm test or use the Extension Test Runner

🔗 Links

VSCode Marketplace - ABLUnit Test Runner
VSCode Marketplace - ABL Developer Pack
Progress Documentation
GitHub Repo - progress/ade - OpenEdge Source Files
Docker Hub - progresssoftware/prgs-oedb - Progress Software Corporation
In the news 📰
- Baltic Amadeus Blog - ABLUnit Testing in VS Code with the ABLUnit Test Runner Extension
My other projects
- BATS Test Runner - Bash Automated Testing System (BATS) test runner

🤓 About Me

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 embrace TDD and improve their code.

ABLUnit Test Runner

Ken Herring