Add regression tests for older PowerShell versions (at least v3+) #96
Labels
0 - Backlog
Issue is accepted, but is not ready to be worked on or not in current sprint
Build Automation
Issues for changes to the build system, without functional changes needed to the project
Tests
Issues related to the tests (NUnit, xUnit, Pester, Etc)
What You Are Seeing?
Per #92, some of the recent changes have broken compatibility with older PowerShell versions on client machines. We should support at least v3 of PowerShell as a minimum, at least I think that's what this collection has historically supported itself (although Chocolatey supports v2 still, so if possible we may want to allow that as well, but I don't know if that's feasible for this collection itself).
What is Expected?
New functionality / refactorings should not break PowerShell compatibility. We should have linting steps in our pipeline or integration testing to verify this. Perhaps we could test against an older Windows version for the Azure client VM we use?
How Did You Get This To Happen? (Steps to Reproduce)
Run the collection's tests against a client machine that is older than Windows 2016.
System Details
N/A
Output Log
N/A
The text was updated successfully, but these errors were encountered: