-
Notifications
You must be signed in to change notification settings - Fork 416
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
Add an example of the proper use of run
with piped commands
#1
Labels
Component: Docs
Priority: Medium
Wrong or misleading documentation, broken behavior with workaround
Type: Enhancement
Projects
Comments
sublimino
pushed a commit
that referenced
this issue
Jul 3, 2018
Bash version via build matrix instead of script loop
sublimino
pushed a commit
that referenced
this issue
Jul 7, 2019
…mino Add extra test and rename some variables
TerraTech
pushed a commit
to TerraTech/bats-core
that referenced
this issue
Apr 6, 2020
…ts from being run This function is intended for the global scope. e.g. #!/usr/bin/env bats -t stop_on_failure [...] This satisfies a testing issue where the first few tests will test critical functions that further tests must rely on being fully stable. For example: 'critical_foo()' is test bats-core#1, and all following tests depend on its operational fitness. If the test bats-core#1 fails, then all following tests are moot.
TerraTech
added a commit
to TerraTech/bats-core
that referenced
this issue
Apr 6, 2020
…ts from being run This function is intended for the global scope. e.g. #!/usr/bin/env bats -t stop_on_failure [...] This satisfies a testing issue where the first few tests will test critical functions that further tests must rely on being fully stable. For example: 'critical_foo()' is test bats-core#1, and all following tests depend on its operational fitness. If the test bats-core#1 fails, then all following tests are moot.
2 tasks
This is in the gotchas now: https://bats-core.readthedocs.io/en/stable/gotchas.html#my-piped-command-does-not-work-under-run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component: Docs
Priority: Medium
Wrong or misleading documentation, broken behavior with workaround
Type: Enhancement
Part of issue creation and project migration effort. From sstephenson/bats #196.
The markdown template for this issue can be found here: Template for issue #1
Related issues:
Related PRs:
What's left to do?
The text was updated successfully, but these errors were encountered: