Skip to content
BC 2026 release wave 2unofficial launch event map, by waldo

Features › Developer tools

Migration from test toolkit events to test handlers

GA · 1 min in 1 video · dev relevance high · documented as Build extensible and data-driven AL test suites low match

Migration from test toolkit events to test handlers

Test handlers are separate from the test toolkit events. Users of those events must migrate to get the new functionality.

Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 1 min across 1 video.

Status evidence

  • Nothing said about status; launch event convention: generally available unless stated otherwise.

Where they talk about it

Quotes

  • 8:27 "these um test handlers are separate from the test toolkit events that are driven by AL test runners" - The new handlers do not replace the old events automatically, so there is a separate mechanism.
  • 8:46 "if you're using those you will need to migrate across to this if you want to take advantage of these functionalities" - Existing event-based test code needs migration to use test handlers.
  • 9:05 "one common use case nowadays for us internally is we use it for managing token consumption" - A practical use case: skipping AI tests when the token or credit budget is used up.

Caveats mentioned

  • Existing test toolkit event subscribers need migrating to use test handlers

Documented features match

  • Build extensible and data-driven AL test suites - low confidence (llm). Docs say: General availability, roadmap id 573333. Handler migration
  • Product documentation (partial, the article describes the broader feature or mentions this in passing): Run AL tests from Visual Studio Code with Test Explorer, checked 2026-10-02. Any tests that rely on events published in a test runner for test setup or teardown might not work. Note: Only an indirect hint (2026 wave 1 article). The lifecycle handlers section never states that test runner events must be migrated.

Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.

Tags: testing, al, migration

Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.