Roadmap

This page lists what AL Runner does not do yet, what waits until users ask for it, and what was decided against. For what works today, see What works and what is refused.

How to move an item up

Each item links to its GitHub issue where one exists. If you need an item, comment on the issue and say what you need it for. Demand from users decides the order. If no issue exists, open one (see Reporting a problem).

Deferred until users ask

These are understood, but they wait for more user demand. Tests that need them are reported as not run, with the reason.

• App translations under another language (issue 5772). AL Runner does not apply an app’s own Translations/*.xlf files. After a test switches GlobalLanguage away from English (1033), a read whose text a translation could change, such as Format of an enum value or a label, is refused.
• --seed. Version 2 printed a random seed and could replay a run with it. Version 3 accepts no --seed and prints none.
• Image.Resize of the System Application (issue 5590). Tests that resize an image are refused.
• Business Central’s development-endpoint test mode (issue 3697). This is the mode that suppresses unhandled UI. AL Runner does not offer it.

Waiting on a change in the Linux test setup

AL Runner checks each behavior against real Business Central before it implements it. Some test isolation cases cannot be measured yet on the Linux Business Central setup that runs those checks. Until they can, their tests are not run:

• --isolation disabled (issue 5609).
• The RequiredTestIsolation cases listed under isolation in Writing tests.

Experimental and off by default

• Building Microsoft’s demo company. The builds of the DemoTool and Contoso companies are on hold and will be redesigned. They run only with --experimental-company-builds. Without it, --company-data demotool, contoso-setup and contoso-all are refused, and the Legacy, IntegrationTest and Uncategorized lanes of --recipe microsoft are reported as not run, with the reason. See Test data.

Not available yet

These features of version 2 do not exist in version 3 yet:

• Finding the app by climbing up from any folder below an app.json. Today a folder without an app.json is an error.
• Running a folder that holds several apps as one run per app. Today each app must be named. Only --affected-from splits a folder of test apps.
• Packaging a folder as an .app without compiling (--emit-app).
• Running a dependency that ships only compiled code, without AL source. Tests that reach such an app are not run, and the message names the app.
• --no-strict-exit (always exit 0). --allow-not-run turns only the exit codes 7 and 8 into 0.
• A note under a failure that names a test-data table that is empty, or the real error behind “The TestPage is not open.”
• Signed binaries. Releases carry SHA256SUMS and build provenance attestations.
• Builds for platforms other than Linux x64, Windows x64 and macOS arm64.

Decided against

• Watch mode (--watch) and its live terminal dashboard. serve keeps the compile warm, and --affected runs only what a change can affect. --watch is refused with a reason. See Editor and tool integration.