To configure SandboxA (an existing environment without the toolkit), you must use the standalone cmdlet Install-TestToolkitToBcContainer. This cmdlet specifically targets an active container by name to deploy the necessary test libraries and objects after the container has already been created.

For SandboxB (being configured from scratch), the New-BcContainer cmdlet is used. To ensure the Test Toolkit is installed during the initial creation and configuration phase, the -includeTestToolkit switch parameter must be included in the command script. This automates the import of the test suite as part of the container lifecycle management.

Microsoft Learn Documentation: "BcContainerHelper PowerShell Module," Reference for New-BcContainer parameters and Install-TestToolkitToBcContainer cmdlet.

Microsoft Dynamics 365 Business Central: "Container-based development environments," Section: Working with Test Toolkits.

GitHub (Official Microsoft/navcontainerhelper Repository): Cmdlet definition for Install-TestToolkitToBcContainer.ps1 and parameter definitions for New-NavContainer.ps1.