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.

Sign up for GitHub

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

Jump to bottom

Improve VS code problem matcher #1452

Closed
nohwnd opened this issue Feb 8, 2020 · 1 comment · Fixed by #1700
Closed

Improve VS code problem matcher #1452

nohwnd opened this issue Feb 8, 2020 · 1 comment · Fixed by #1700
Milestone
5.x

Comments

@nohwnd
Copy link
Member

nohwnd commented Feb 8, 2020 •
edited
Loading

Skipping problem matching in the current implementation of VSCode integration. enable vscode marker and options.
@nohwnd nohwnd modified the milestones: 5.x, 5.0-beta, 5.0 Feb 8, 2020
@nohwnd nohwnd modified the milestones: 5.0, 5.x Mar 28, 2020
@fourpastmidnight
Copy link
Contributor

For the Gherkin side of things, I have improved how errors are reported so that problem matchers are easily created. This is part of #1276, which I've come back here to once again attempt to get merged. One of the comments on that PR show the problem matchers I'm using for the Gherkin side of things.

Perhaps similar code or problem matchers would work for the RSpec runner?

@fflaten fflaten mentioned this issue Sep 2, 2020
Closed
@fflaten fflaten mentioned this issue Oct 1, 2020
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
5.x
Development

Successfully merging a pull request may close this issue.

Add support for VSCode problem-tracking for failed assertions fflaten/Pester
2 participants
@nohwnd @fourpastmidnight