-
Notifications
You must be signed in to change notification settings - Fork 27
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
Support @skipif directive #116
Comments
Note making vroom tests too conditional could quickly get out of hand, with long vroom files being so linear and stateful. Might decide a feature like this would be too hard to get right and not worth building. An alternative that's already supported is to keep all the conditional stuff in separate files and have the test runner scripts conditionally |
Counter proposal: It would be really handy to be able to point Making it only valid as the first directive encourages test decomposition, and also greatly simplifies the interpreter as it can just stop immediately. It would also be simple to implement the directive as "skip the rest of the file". I would be very opposed to vroom guessing where to resume tests (if |
Ooh, yeah, I'd thought about doing it as an early exit mechanism but not about making it just a file-level directive. |
Sometimes a section of vroom testing only makes sense to run in certain conditions (particular versions of vim etc.). It would be useful to have a
@skipif CONDITION
directive that could evaluate a vimscript expression and conditionally skip some vroom lines.Example:
Then this could note in the test summary output that it passed but with some skipped portions.
The text was updated successfully, but these errors were encountered: