Add compatibility tests for ConvertTo-Json by yotsuda · Pull Request #26639 · PowerShell/PowerShell
7 tasks
This was referenced
yotsuda added a commit to yotsuda/PowerShell that referenced this pull request
…o-Json Add 34 new Pester tests covering: - Depth parameter basic behavior (default and explicit depth values) - Depth truncation with arrays and hashtables - Depth truncation string representations - Multilevel compositions (Array/Dictionary/PSCustomObject/Class) - Complex nested mixed type structures - Pipeline vs InputObject behavior This is Phase 4 of the test plan from PR PowerShell#26639. Co-Authored-By: Claude <noreply@anthropic.com>
yotsuda added a commit to yotsuda/PowerShell that referenced this pull request
…o-Json Add 34 new Pester tests covering: - Depth parameter basic behavior (default and explicit depth values) - Depth truncation with arrays and hashtables - Depth truncation string representations - Multilevel compositions (Array/Dictionary/PSCustomObject/Class) - Complex nested mixed type structures - Pipeline vs InputObject behavior This is Phase 4 of the test plan from PR PowerShell#26639. Co-Authored-By: Claude <noreply@anthropic.com>
yotsuda added a commit to yotsuda/PowerShell that referenced this pull request
…o-Json Add 34 new Pester tests covering: - Depth parameter basic behavior (default and explicit depth values) - Depth truncation with arrays and hashtables - Depth truncation string representations - Multilevel compositions (Array/Dictionary/PSCustomObject/Class) - Complex nested mixed type structures - Pipeline vs InputObject behavior This is Phase 4 of the test plan from PR PowerShell#26639. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters