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

fix: TAP Schema treats SKIP as a directive, at the end of the line #262

Merged
merged 1 commit into from
Nov 18, 2020
Merged

fix: TAP Schema treats SKIP as a directive, at the end of the line #262

merged 1 commit into from
Nov 18, 2020

Commits on Nov 16, 2020

  1. fix: TAP Schema treats SKIP as a directive, at the end of the line 

    Playing around with tap-to-junit vlaidations I found that the only safe way
to get the skips parsed was to use capitalized `# SKIP` with the space after
the description.

Technically lowercase seems to be allowed but the majority of the schema's
examples show capitalized.

In the schema it also says any explanation of why it was skipped should go
after the `# SKIP`, but the description of the test still goes to the left.

https://testanything.org/tap-version-13-specification.html
    @gregswift
    gregswift committed Nov 16, 2020
    Configuration menu
    Copy the full SHA
    22b50e1 View commit details
    Browse the repository at this point in the history