AL TestScribe captures failures from your normal AL test run and preserves them as local reports. No runner replacement. No cloud upload. No opinion about what you do with the result.
al-test-failures.mdExpected: 1
Actual: 0
Assertion failed while validating posted shipment lines.
Test error retained in full, ready for review in the report file.
AL TestScribe adds a durable record to the workflow you already trust. It observes failures after the AL service has handled them, then writes only the formats you selected.
No telemetry, no network upload, and no automatic sharing. Commit, attach, parse, or ignore the files on your own terms.
The original AL test-service call happens first. TestScribe records what follows, without replacing notification handlers.
User and timestamp folders preserve prior reports instead of treating the latest run as the only one that matters.
Choose automatic export for continuous evidence, or manual export when you decide a capture is ready. Both modes confirm a successful write in VS Code.
Use your existing Business Central AL test workflow inside VS Code.
TestScribe records the test, codeunit, duration, timestamp, and complete service error.
Automatic mode writes after each failure. Manual mode waits for the export command.
Open the saved file and decide how, or whether, to use the evidence.
One run creates the reports you choose. Markdown, JSON, and CSV carry the same captured facts in formats suited to different destinations.
Markdown is ideal for review. JSON works for scripts and structured processing. CSV is ready for tabular analysis. Configure one, two, or all three per workspace.
tools/al-test-scribe-results/
carlos/
2026-07-28_14-35-42-123/
al-test-failures.md
al-test-failures.json
al-test-failures.csv
carlos/
2026-07-29_09-12-04-826/
al-test-failures.md
Install AL Language, open an AL workspace containing app.json, then install AL TestScribe. Run a failed test and your first local report is written automatically.