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

Add an example of the proper use of run with piped commands #1

Closed
btamayo opened this issue Sep 20, 2017 · 1 comment
Closed

Add an example of the proper use of run with piped commands #1

btamayo opened this issue Sep 20, 2017 · 1 comment
Labels
Component: Docs Priority: Medium Wrong or misleading documentation, broken behavior with workaround Type: Enhancement
Projects

Comments

@btamayo
Copy link
Member

btamayo commented Sep 20, 2017

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:

  1. bats script not working sstephenson/bats#69
  2. Pipe does not work in the test sstephenson/bats#10

Related PRs:

  1. added example of piping commands together with run sstephenson/bats#47

What's left to do?

Step Status
1. Assigned Not needed
2. PR Created #47
3. ⚠️ PR pointed to bats-core/bats Pending
4. Approval
@btamayo btamayo added this to PR needs repointing in Road to 1.0 Sep 20, 2017
mbland pushed a commit that referenced this issue Mar 16, 2018
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.
@martin-schulze-vireso martin-schulze-vireso added Priority: Medium Wrong or misleading documentation, broken behavior with workaround Type: Enhancement labels Oct 23, 2021
@martin-schulze-vireso
Copy link
Member

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
Projects
No open projects
Road to 1.0
PR needs repointing
Development

No branches or pull requests

2 participants