Skip to content

Conversation

@djweber
Copy link

@djweber djweber commented Oct 9, 2017

Currently, if a user does not clone with the --recursive flag or run
git submodule update --init, Start-PSPester will fail to run due to
the Pester module missing. While the errorhints at the Pester module not
being found, there is no suggested way of fixing the issue presented to
the user.

Currently, if a user does not clone with the --recursive flag or run
git submodule update --init, Start-PSPester will fail to run due to
the Pester module missing. While the errorhints at the Pester module not
being found, there is no suggested way of fixing the issue presented to
the user
@djweber djweber closed this Oct 9, 2017
@djweber djweber deleted the pester_warning branch October 9, 2017 21:13
[switch]$IncludeFailingTest
)

if (-not (Test-Path $Pester)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you would need to run git submodule status and read the status

@djweber
Copy link
Author

djweber commented Oct 10, 2017

Ancestor of #5069. Had an issue with a deleted submodule, so I closed this and made a new PR.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants