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

Update to Pester v5.2.1 #443

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from
Draft

Update to Pester v5.2.1 #443

wants to merge 9 commits into from

Conversation

vexx32
Copy link
Owner

@vexx32 vexx32 commented May 6, 2021

PR Summary

Update to Pester v5 and take advantage of the Run.SkipRun features added to remove some of the awfully hacky discovery-only code we needed in older Pester versions.

Resolves #413

Context

Pester v5.2.0 added options to allow us to natively skip the actual Run phase and just get test metadata back. This makes the necessary changes to use the functionality properly, instead of relying on unsupported and hacky methods of getting that data.

Changes

  • Removed Measure-KoanTestBlock
  • Updated Measure-Koan
  • Updated Pester dependency to 5.2.0
  • Update and re-enable tests for Measure-Koan
  • Version bump to 0.68.0

Checklist

  • Pull Request has a meaningful title.
  • Summarised changes.
  • Pull Request is ready to merge & is not WIP.
  • Added tests / only testable interactively.
    • Make sure you add a new test if old tests do not effectively test the code changed.
  • Added documentation / opened issue to track adding documentation at a later date.

vexx32 added 4 commits May 6, 2021 09:13
Pester v5.2.0 added the ability to natively run just the discovery phase
of a test suite, so we refactor Measure-Koan to utilize this and save
doing a lot of manual work.

This also obsoletes the private Measure-KoanTestBlock command that
previously supported Measure-Koan. Pester automatically does that
calculation on its own before presenting the discovery results. This
command has been removed as a result.
In some cases it looks like Pester can fail to publish if there are too
many versions of Pester available. Prevent this by checking the version
we actually need and publishing just that version when doing a publish
to the filesystem.

Also set the initially installed version of pester to the correct
version based on the current required version specified by PSKoans
itself, instead of having to update the environment-setup.yml each time.
@vexx32 vexx32 added Category-Build 🚀 Modifies the build / deployment system Category-Module Pertaining to the module's functionality itself. labels May 6, 2021
@vexx32 vexx32 closed this May 15, 2021
@vexx32 vexx32 reopened this May 15, 2021
@vexx32 vexx32 changed the title Update to Pester v5.2.0 Update to Pester v5.2.1 May 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category-Build 🚀 Modifies the build / deployment system Category-Module Pertaining to the module's functionality itself.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pester v5
1 participant