What's New : AL-Go for GitHub on Quality and Testability (2025 release wave 1)
AL-Go for GitHub (2025 release wave 1) can now run page scripting tests in workflows. It uses the BC replay npm module shipped in 2024 Wave 2, configured by a project setting that points to recording folders or files, and adds a page scripting test result visualizer. It can also deploy test apps to sandbox environments and exclude apps by ID. Test apps whose dependencies are not in AppSource are skipped automatically. Automatically running tests after deployment is planned but not yet implemented.
- Introduction and Page Scripting Tests Overview
- Page Scripting Test Support and BC Replay Module
- Page Scripting Test Demo and Configuration
- Test Result Visualization
- Test Apps Deployment Feature Overview
- Test Apps Deployment Demo
- Custom Deployment Scripts and Conclusion
Overview
The video covers AL-Go for GitHub changes focused on quality and testability in 2025 release wave 1. The first part shows how page scripting tests run in the AL-Go workflow with the BC replay npm module, how recordings are configured in project settings, and how results appear in a visualizer with downloadable artifacts.
The second part covers deploying test apps alongside production apps to sandbox environments, excluding apps by ID, and how test apps are handled in custom deployment scripts. The presenter notes that automatically running tests is covered only in a first version for this presentation.
Key points
- Page scripting tests run in the AL-Go workflow through the BC replay npm module, which shipped in 2024 Wave 2.
- Recordings are generated in Business Central. A page scripting test project setting points to them. It is an array (several folders), picks up .yml files, and supports pattern matching or a single specific file.
- The new page scripting test result visualizer shows whether each test passed. For failures, the downloadable result artifact’s extended logs include a video of the test.
- Test apps can be deployed alongside apps when deploying to a sandbox environment. You enable include test apps in sandbox environment in the deploy to structure of the AL-Go settings.
- The new exclude app IDs array in the deploy to structure leaves specific apps out of deployment.
- Test apps that depend on something not available in the AppSource gallery are automatically detected and excluded during deployment.
- With the setting enabled, test apps are passed to custom deployment scripts, and the script must handle dependency installation.
Features
| Feature | Status | At |
|---|---|---|
| Page Scripting Tests in AL-Go Workflow | status not stated, demoed | 0:25 |
| Page Scripting Test Result Visualizer | status not stated, demoed | 2:34 |
| Deploy Test Apps to Sandbox | status not stated, demoed | 3:15 |
| Exclude Apps by ID During Deployment | status not stated, demoed | 3:46 |
| Automatic Test App Dependency Resolution | status not stated, demoed | 5:15 |
| Page Scripting Test Settings Configuration | status not stated, demoed | 1:53 |
| Custom Deployment Script Test App Support | status not stated | 5:35 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- other “BC replay npm module” at 0:46
- other “page scripting test settings” at 1:53
- other “test result visualizer” at 2:34
- other “page scripting test result visualizer” at 2:34
Quotes
- 0:25 “we actually added support for page scripting tests”
- 0:46 “half a year ago in version 2024 Wave 2 we shipped the BC replay npm module with that module it’s possible to to run”
- 3:15 “we have two features we want to support number one is deploying test apps uh and number two is automatically running tests”
- 3:46 “we now also have the option to exclude apps by ID when you deploy”
Disclaimers in the video
- 3:15 not-in-this-release: number two is automatically running tests for this presentation we have implemented the first version
Presenters (as heard): Freddy Christensen, Sebastian.