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

Fix IncludeVSCodeMarker #726

Merged
merged 20 commits into from
Mar 2, 2017
Merged

Conversation

Jaykul
Copy link
Contributor

@Jaykul Jaykul commented Feb 9, 2017

Put the stack trace at the top when IncludeVSCodeMarker is set in PesterOptions:

Invoke-Gherkin -PesterOption @{ IncludeVSCodeMarker = $true }
or
Invoke-Pester -PesterOption @{ IncludeVSCodeMarker = $true }

Jaykul added 13 commits January 30, 2017 02:27
Removed "BeforeAllFeatures" and "AfterAllFeatures" hooks that didn't actually work right
Updated tests to match
This way, Pester's default output shows the "Could not find" message!
I cannot explain why, but it fixes a generics type reference in PowerShell 2
Put the .feature location into the "stack" on failures.
Refactor Import-GherkinFeature to add the path to the location
Add and fix tests showing that the gherkin scope works as expected
@Jaykul Jaykul force-pushed the IncludeVSCodeMarker branch from fac3eae to ef380ee Compare February 11, 2017 22:17
I'm a little worried about this -- should I be renaming all the variables?
@dlwyatt dlwyatt merged commit 8a8618c into pester:DevelopmentV4 Mar 2, 2017
@Jaykul Jaykul deleted the IncludeVSCodeMarker branch March 4, 2017 20:33
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