Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Serialized xml is nested too deeply - TestToolkit

Open
#8,353 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
powershell
Domain
tooling

Research direction

Start by reproducing the reported error with the supplied PowerShell script and -includeTestToolkit, then compare it with the Import-TestToolkitToBcContainer command mentioned in the report. The issue does not identify repository files or tests, so locate the relevant TestToolkit import/container entry points before tracing the XML serialization failure. Done means the container can be created with the Test Toolkit without the nested-XML error.

Written by the indexing model from the issue text.

Description

1. Describe the bug

I am getting the "Serialized xml is nested too deeply" error message when I create a docker container using a PowerShell script. The script includes the -includeTestToolkit flag.

2. To Reproduce
Steps to reproduce the behavior:

  1. Execute the following script

/*********************** Script begins ************************/

install-module BcContainerHelper -force

$accept_eula = $true
$containername = 'bc29'
$licenseFile = ''
$auth = 'Windows'
$usessl = $false
$updateHosts = $true
$assignPremiumPlan = $true
$shortcuts = 'Desktop'
$bcVersion = '29.0.0.0'

$artifactUrl = Get-BcArtifactUrl -type 'Sandbox' -country 'CA' -version $bcVersion -select 'Closest' -accept_insiderEula -storageAccount bcinsider

if ($auth -eq 'Windows') {
$credential = get-credential -UserName $env:USERNAME -Message 'Using Windows Authentication. Please enter your Windows credentials.'
}
elseif ($auth -eq 'UserPassword') {
$credential = get-credential -Message 'Using Username/Password Authentication. Please enter credentials.'
}
else {
throw '$auth needs to be either Windows or UserPassword'
}

if (!$accept_eula) {
throw 'You have to accept the eula in order to create a Container.'
}
if (!($containername)) {
throw 'You have to specify a container name in order to create a container.'
}
if (!($artifactUrl)) {
throw 'No matching build was found for your version of Business Central'
}
New-BcContainer -accept_eula:$accept_eula -accept_insiderEula
-containername $containername -artifactUrl $artifactUrl
-auth $auth -Credential $credential
-usessl:$usessl -updateHosts:$updateHosts
-licenseFile $licenseFile -assignPremiumPlan:$assignPremiumPlan
-shortcuts $shortcuts `
-includeTestToolkit

if ($licenseFile) {
Setup-BcContainerTestUsers -containerName $containername -password $credential.Password
}

/*********************** Script ends ************************/

3. Expected behavior
The docker container should be created without any errors and include all the Tests extensions.

4. Actual behavior
Le XML sérialisé est imbriqué trop profondément. Line 1, position 3605. (Serialized xml is nested too deeply. Line 1, position 3605.)
Image

NOTE: I also tried to the following command:

Import-TestToolkitToBcContainer -containerName bc29 -includeTestRunnerOnly and got the following result:

Image

5. Versions:

  • AL Language: 18
  • Visual Studio Code: N/A
  • Business Central: 29.0.52454.0
  • List of Visual Studio Code extensions that you have installed: None
  • Operating System:
    • Windows
    • Linux
    • MacOS
Dominant language
PowerShell
Stars
884
Forks
285
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/AL

All issues in microsoft/AL

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.