Skip to content

Move to new Pester version #3002

Description

@iSazonov

Now Pester v3.4.5 support output filters pester/Pester#645. We can use this to reduce the CI output.

Currently we use very old Pester version 3.3.9 (May 23, 2015) so perhaps the time has come to move to new version.

Activity

  1. mirichmo commented on Jan 17, 2017

    @mirichmo
    Member

    James Truher (@JamesWTruher) and Aditya Patwardhan (@adityapatwardhan) - Have you guys investigated moving to a later version of Pester?

  2. modified the milestones: , on Mar 5, 2017
  3. iSazonov commented on Mar 11, 2017

    @iSazonov
    CollaboratorAuthor

    Joey Aiello (@joeyaiello) I wonder shall we distribute PowerShell 6 RTM with old Pester? Should we add this in Plan?

  4. joeyaiello commented on Mar 27, 2017

    @joeyaiello
    Contributor

    As far as I understood from James Truher (@JamesWTruher), the plan was always to be conservative with picking up new versions of Pester. Basically, that we shouldn't ship a new one unless we had a reason to pick up the new stuff.

    It may very well be the case that we need to do that, but I'd like Jim to come in and make sure I've got the history right first.

  5. iSazonov commented on Mar 27, 2017

    @iSazonov
    CollaboratorAuthor

    I agree that conservatism here is good. But two years is too much.

    There is another problem. If Windows users can easily upgrade Pester and exploit new features, the Unix users cannot do this. This is really a problem for those who want to be fully ported.

  6. iSazonov commented on May 25, 2017

    @iSazonov
    CollaboratorAuthor

    Related #1371

  7. SteveL-MSFT commented on Nov 13, 2017

    @SteveL-MSFT
    Member
  8. JamesWTruher commented on Nov 14, 2017

    @JamesWTruher
    Collaborator

    I've been looking at Pester 4.0.8 and it looks really great. Lot's of excellent improvements; First and foremost handling our cross-plat needs, but it's not completely backwardly compatible, and I get more than 100 test failures when I run our tests using 4.0.8. I've got a big bunch of them fixed and all of those are test issues, but it's taking a bit of time to track them all down.

    The issues boil down to a couple of things - missing/changed assertions (Contains/FileContentMatch), Be actually working against arrays (awesome), and tests which never actually worked, and because error checking has improved to catch them, like Should Throw which now complains if it doesn't get a scriptblock, those tests are properly failing.

    I do look forward to the time when we can just grab this and dump our submodule and it shouldn't be too long now. Dave Wyatt (@dlwyatt) Is there any thought of making this a nupkg?

  9. dlwyatt commented on Nov 14, 2017

    @dlwyatt
    Contributor

    James Truher (@JamesWTruher) Pester is published to nuget.org, Chocolatey and the PowerShell Gallery. Technically all three of those are nuget feeds; take your pick. :)

  10. JamesWTruher commented on Nov 15, 2017

    @JamesWTruher
    Collaborator
  11. it-praktyk commented on Jan 6, 2018

    @it-praktyk
    Contributor

    Pester since v. 4.1.0 is supported at PSCore 6.0 for all platforms (Linux, macOS, Windows - in alphabetical order).

  12. iSazonov commented on Feb 9, 2018

    @iSazonov
    CollaboratorAuthor

    Fixed in #6064

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions