PR Summary

The current json tests do not adequately test datetimes and integers and while there are some unit tests for primitives there are no "large object" tests. I created a little test generator to take an object and produce tests using the various formats.

The datetime tests also do specific things in the case that newtonsoft chooses to convert the json string into a datetime versus when it does not.

The complex object test makes sure that our unit tests apply even when the object is large, with a variety of types and with nested arrays and objects.

The number tests make sure that we properly capture when newtonsoft decides to give us int64 vs double vs bigint objects.

This will make it apparent when changes to the deserializer cause a difference in behavior for datetime , numbers or complex objects.

PR Context

Improve test coverage for json cmdlets. These tests document current behavior and do not have an opinion on what correct behavior looks like. These will help with a future move to system.text.json in understanding where the differences in deserialization are.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: