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

(maint) A few minor updates #3589

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from
Draft

Conversation

corbob
Copy link
Member

@corbob corbob commented Dec 6, 2024

Description Of Changes

  • Remove the mention of choco list -lo from the NuSpec file.
  • Update an upgrade all test to ensure that it does not report failure if a newer Chocolatey version is available on internal repositories.

Motivation and Context

  • Local Only on the list command was removed in 2.0, and is an error now.
  • When tests are running as we come up towards a release, we end up with reports of failures of the upgrade all command because for instance it will be testing version 2.4.1-beta-20241204, but because of the way the builds work, CI will have build and published to our repository version 2.5.0-alpha-20241204 which is deemed an upgrade for the pre-release version being tested.

Testing

  • Run through Test Kitchen
  • Run tests through vagrant up in the tests directory.

Operating Systems Testing

  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

Change Types Made

  • Bug fix (non-breaking change).
  • Feature / Enhancement (non-breaking change).
  • Breaking change (fix or feature that could cause existing functionality to change).
  • Documentation changes.
  • PowerShell code changes.
  • Pester test changes.

Change Checklist

  • Requires a change to the documentation.
  • Documentation has been updated.
  • Tests to cover my changes, have been added.
  • All new and existing tests passed?
  • PowerShell code changes: PowerShell v3 compatibility checked?

Related Issue

N/A - These are things that I found doing the recent 2.4.1 release.

Sometimes tests in Test Kitchen are run against versions of Chocolatey
that are available on the setup repository, and so they are found as
part of upgrade testing. The tests don't need these newer Chocolatey
versions, nor do we expect to find them. This excludes all of the
packages that are known to be on testing environments but not part of
the test in question.

This is to reduce the number of false positive tests we have, especially
as we come up to a release.
@corbob corbob added the NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product. label Dec 6, 2024
@corbob corbob self-assigned this Dec 6, 2024
@corbob
Copy link
Member Author

corbob commented Dec 6, 2024

This PR is draft until I can run the tests through Test Kitchen. I also need to update the testing steps to validate that the test failure is gone, but will need to think on the best way to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant