Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add regression tests for older PowerShell versions (at least v3+) #96

Open
vexx32 opened this issue Aug 15, 2022 · 1 comment
Open

Add regression tests for older PowerShell versions (at least v3+) #96

vexx32 opened this issue Aug 15, 2022 · 1 comment
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)

Comments

@vexx32
Copy link
Member

vexx32 commented Aug 15, 2022

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

@vexx32 vexx32 added Build Automation Issues for changes to the build system, without functional changes needed to the project 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Tests Issues related to the tests (NUnit, xUnit, Pester, Etc) labels Aug 15, 2022
@jborean93
Copy link
Contributor

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)

Ansible itself can only run on v3 or newer so you don't have to have v2 support as it shouldn't be possible to actually run it on that version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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)
Projects
None yet
Development

No branches or pull requests

2 participants