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

Show failure location even if windows driver letter is lowercase #329

Merged
merged 1 commit into from
Jan 28, 2019
Merged

Conversation

mkls
Copy link
Contributor

@mkls mkls commented Oct 17, 2016

I had a fix for this issue not so long ago (#316), but as it turns out, on our work machines the driver letter is lowercase, so I wasn't able to impress my colleagues with this new (to them) feature of tape.
Probably should have tried it there instead of just on my home PC, but better later than never.

Copy link
Collaborator

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

Seems reasonable.

I don't think this is covered by tests, so this should be fine.

@ljharb ljharb merged commit fb548b3 into tape-testing:master Jan 28, 2019
ljharb added a commit that referenced this pull request Feb 9, 2019
[New] Implements TAP TODO directive (#254)
[New] add alias 'notDeepEquals' to 'notDeepEqual' function (#411)

[Fix] fix premature end of tests (and running sibling tests) when test includes subtests (#403, #222)
[Fix] only use one test runner for results, even if multiple streams are created (#404, #361, #105)
[Fix] windows: Show failure location even if driver letter is lowercase (#329)

[Docs] link to mixed tape (#445)
[Docs] Add electron-tap (#240)
[Docs] Add tape-promise into 'other' (#210)
[Docs] Mention [`flip-tape`](https:/pguth/flip-tape/blob/master/README.md) in the section "other". (#359)
[Docs] Add an alternative ES6 tape runner (#328)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants