[Bug]: Run-TestsInBcContainer fails with "Cannot open page 130455" on BC 27.5 — Import-TestToolkitToBcContainer reports success but does not install Tests-TestRunner

[JaniEnora]

BCContainerHelper version

6.1.11

Describe the issue

On BC 27.5 sandbox artifacts (country: NO), Import-TestToolkitToBcContainer completes and prints "TestToolkit successfully imported", but Run-TestsInBcContainer immediately fails with:

Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\BcContainerHelper\Extensions\...\PsTestTool and retry. You might also have URL or Company name wrong.

The root cause is that Import-TestToolkitToBcContainer only installs Tests-TestLibraries and AI Test Toolkit — it does not install Tests-TestRunner. However, Run-TestsInBcContainer (PsTestFunctions.ps1: line 598) still tries to open page 130455, which lives in Tests-TestRunner. Since Tests-TestRunner is absent from BC 27.5 artifacts (replaced by AI Test Toolkit), the page does not exist and the run fails.

Steps to reproduce

1. Create a BC 27.5 container with installTestRunner=$true, installTestFramework=$true, installTestLibraries=$true via Run-AlPipeline (e.g. via AL-Go v8.1)
2. Observe that Tests-TestLibraries and AI Test Toolkit are installed, but not Tests-TestRunner
3. Import-TestToolkitToBcContainer reports TestToolkit successfully imported
4. Run-TestsInBcContainer fails: Cannot open page 130455

Artifact used

https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/sandbox/27.5.46862.47891/no

Installed apps after import (relevant)

App ID	Name	Installed
5d86850b-0d76-4eca-bd7b-951ad998e997	Tests-TestLibraries	✅
2156302a-872f-4568-be0b-60968696f0d5	AI Test Toolkit	✅
(classic test runner)	Tests-TestRunner	❌ missing

Expected behavior

Either:

• Run-TestsInBcContainer should detect that AI Test Toolkit is installed and use its page instead of 130455, or
• Import-TestToolkitToBcContainer should still install Tests-TestRunner if present in the artifacts, and only fall back to AI Test Toolkit if it is not

Stack trace

at Run-TestsInBcContainer, BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-TestsInNavContainer.ps1: line 598
at <ScriptBlock>, Run-AlPipeline.ps1: line 1231
at Run-AlPipeline, Run-AlPipeline.ps1: line 1270

Additional context

• Triggered via AL-Go v8.3 on a GitHub Actions runner (Windows Server 2025, hyperv isolation)
• Container creation log shows includeTestToolkit=False (expected — toolkit is imported separately)
• The import group ##[group]Importing test toolkit runs for ~113 seconds, installs TestLibraries and AI Test Toolkit, then exits with "TestToolkit successfully imported" — no error
• ~90 seconds later, Run-TestsInBcContainer fails at page 130455

[JaniEnora]

Update after further investigation — the root cause is different from the original description.

After extracting and inspecting all apps in the BC 27.5 NO sandbox artifact (27.5.46862.48004), page 130455 ("Command Line Test Tool") does not exist in any app. It was not moved — it was removed entirely.

In BC 27.5:

• Test Runner (app ID 23de40a6) — same app ID as the old Tests-TestRunner, but now contains 0 pages (only runtime codeunits)
• TestRunner-Internal (app ID 538ca7e3) — new app, contains UI pages 130020–130029, 130202–130203 but not page 130455

Root cause: Microsoft removed the page-based CLI test runner (page 130455) in BC 27.5. The replacement appears to be codeunit-based: CLI Test Runner (codeunit 130201) in TestRunner-Internal, which delegates to Snap Test Runner.

What needs to change in navcontainerhelper: Run-TestsInBcContainer needs a BC 27.5-aware code path that does not rely on page 130455. The codeunit-based runner (CLI Test Runner, 130201) in TestRunner-Internal is the likely replacement mechanism.