Skip to content

Minor issues with Restore-PSPester #6143

Closed

Description

@anmenaga

build.psm1 was recently updated to use 'Save-Module' in Restore-PSPester #6112
Side effects of this update broke Docker package validation tests.
Specifically:

  1. Now Restore-PSPester requires-Destinationdirectory to exist and throws error if it doesn't; Previously Restore-PSPester was creating it.
    restorepester0

  2. Default -Destination directory is NOT based on PSModulePath, but rather on a (Get-PSOptions -DefaultToNew).Output, which is not helpful at all since it requires to provide full path to the module in case pwsh is run from an installed package as opposed to built from clone repo.
    restorepester1

Activity

  1. SteveL-MSFT commented on Feb 9, 2018

    @SteveL-MSFT
    Member

    We shouldn't rely on Restore-PSPester anymore sine we've updated the tests to be compatible with Pester 4.x. We should probably have Start-PSPester install Pester from PSGallery if it's not installed.

  2. iSazonov commented on Feb 10, 2018

    @iSazonov
    Collaborator

    I don't still test - Is this works for VS Code debugging? - there another output path is.

  3. added
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on Feb 20, 2018
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

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-FixedThe issue is fixed.WG-Maintainers-Buildspecific to affecting the build

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions