5e1a4b3129
Updated all Pester tests in the project to support Pester v5. The main benefit that we get out of this, besides just moving on to the currently supported version of the test framework, is that we can now execute individual tests directly within VS Code. In the process of doing this migration: * Removed repository Code of Conduct tests from GitHubMiscellaneous.tests.ps1 since the command has been deprecated by GitHub * Updated GitHubReleases.tests.ps1 to account for pre-releases * Updated run-unitTests.yaml and CONTRIBUTING.md to have the Pester v5.3.3 install command, as well as to update its invocation commands. * Removed the language-specific error messages in some `-Throws` tests because the wording keeps changing. * Updated this project's VSCode settings.json to take advantage of the fact that the tests are now Pester 5 compatible. This allows each individual block to have a Run/Debug link associated with it. ([More info](https://pester.dev/docs/usage/vscode)). * Disabled all of the Projects/ProjectCards/ProjectColumns tests because Classic Projects have been deprecated by GitHub (#380 for more info) Fixes #194 Co-authored-by: Howard Wolosky <HowardWolosky@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| launch.json | ||
| settings.json | ||