Running tests with bash 3.1.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✗ invalid filename prints an error
   (in test file test/bats.bats, line 26)
     `[ $status -eq 1 ]' failed
 ✗ empty test file runs zero tests
   (in test file test/bats.bats, line 33)
     `[ "$output" = "1..0" ]' failed
 ✗ one passing test
   (in test file test/bats.bats, line 39)
     `[ "${lines[0]}" = "1..1" ]' failed
 ✗ summary passing tests
   (in test file test/bats.bats, line 46)
     `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
 ✗ summary passing and skipping tests
   (in test file test/bats.bats, line 52)
     `[ "${lines[2]}" = "2 tests, 0 failures, 1 skipped" ]' failed
 ✗ summary passing and failing tests
   (in test file test/bats.bats, line 58)
     `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
 ✗ summary passing, failing and skipping tests
   (in test file test/bats.bats, line 64)
     `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
 ✗ one failing test
   (in test file test/bats.bats, line 69)
     `[ $status -eq 1 ]' failed
 ✗ one failing and one passing test
   (in test file test/bats.bats, line 78)
     `[ $status -eq 1 ]' failed
 ✗ failing test with significant status
   (in test file test/bats.bats, line 88)
     `[ $status -eq 1 ]' failed
 ✗ failing helper function logs the test case's line number
   (in test file test/bats.bats, line 94)
     `[ $status -eq 1 ]' failed
 ✓ test environments are isolated
 ✗ setup is run once before each test
   (in test file test/bats.bats, line 111)
     `[ ${#lines[@]} -eq 3 ]' failed
 ✗ teardown is run once after each test, even if it fails
   (in test file test/bats.bats, line 117)
     `[ $status -eq 1 ]' failed
 ✗ setup failure
   (in test file test/bats.bats, line 124)
     `[ $status -eq 1 ]' failed
 ✗ passing test with teardown failure
   (in test file test/bats.bats, line 132)
     `[ $status -eq 1 ]' failed
 ✗ failing test with teardown failure
   (in test file test/bats.bats, line 140)
     `[ $status -eq 1 ]' failed
 ✗ teardown failure with significant status
   (in test file test/bats.bats, line 148)
     `[ $status -eq 1 ]' failed
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✗ load aborts if the specified script does not exist
   (in test file test/bats.bats, line 166)
     `[ $status -eq 1 ]' failed
 ✓ load sources scripts by absolute path
 ✗ load aborts if the script, specified by an absolute path, does not exist
   (in test file test/bats.bats, line 176)
     `[ $status -eq 1 ]' failed
 ✗ output is discarded for passing tests and printed for failing tests
   (in test file test/bats.bats, line 181)
     `[ $status -eq 1 ]' failed
 ✗ -c prints the number of tests
   (in test file test/bats.bats, line 190)
     `[ "$output" = "0" ]' failed
 ✗ dash-e is not mangled on beginning of line
   (in test file test/bats.bats, line 200)
     `[ "${lines[1]}" = "ok 1 dash-e on beginning of line" ]' failed
 ✓ dos line endings are stripped before testing
 ✗ test file without trailing newline
   (in test file test/bats.bats, line 211)
     `[ "${lines[1]}" = "ok 1 truth" ]' failed
 ✗ skipped tests
   (in test file test/bats.bats, line 217)
     `[ "${lines[1]}" = "ok 1 # skip a skipped test" ]' failed
 ✓ extended syntax
 ✓ pretty and tap formats
 ✗ pretty formatter bails on invalid tap
   (in test file test/bats.bats, line 244)
     `[ $status -eq 1 ]' failed
 ✗ single-line tests
   (in test file test/bats.bats, line 251)
     `[ $status -eq 1 ]' failed
 ✗ testing IFS not modified by run
   (in test file test/bats.bats, line 263)
     `[ "${lines[1]}" = "ok 1 loop_func" ]' failed
 ✗ executing exported function does not break failing test output
   (in test file test/bats.bats, line 270)
     `[ $status -eq 1 ]' failed
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✗ running an ad-hoc suite by specifying multiple test files
   (in test file test/suite.bats, line 48)
     `[ "${lines[0]}" = "1..3" ]' failed
 ✓ extended syntax in suite

45 tests, 29 failures

Running tests with bash 3.2.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✓ invalid filename prints an error
 ✓ empty test file runs zero tests
 ✓ one passing test
 ✓ summary passing tests
 ✓ summary passing and skipping tests
 ✓ summary passing and failing tests
 ✓ summary passing, failing and skipping tests
 ✓ one failing test
 ✓ one failing and one passing test
 ✓ failing test with significant status
 ✓ failing helper function logs the test case's line number
 ✓ test environments are isolated
 ✓ setup is run once before each test
 ✓ teardown is run once after each test, even if it fails
 ✓ setup failure
 ✓ passing test with teardown failure
 ✓ failing test with teardown failure
 ✓ teardown failure with significant status
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✓ load aborts if the specified script does not exist
 ✓ load sources scripts by absolute path
 ✓ load aborts if the script, specified by an absolute path, does not exist
 ✓ output is discarded for passing tests and printed for failing tests
 ✓ -c prints the number of tests
 ✓ dash-e is not mangled on beginning of line
 ✓ dos line endings are stripped before testing
 ✓ test file without trailing newline
 ✓ skipped tests
 ✓ extended syntax
 ✓ pretty and tap formats
 ✓ pretty formatter bails on invalid tap
 ✓ single-line tests
 ✓ testing IFS not modified by run
 ✗ executing exported function does not break failing test output
   (in test file test/bats.bats, line 273)
     `[ "${lines[2]}" = "# (in test file test/fixtures/bats/exported_function.bats, line 9)" ]' failed
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✓ running an ad-hoc suite by specifying multiple test files
 ✓ extended syntax in suite

45 tests, 1 failure

Running tests with bash 4.0.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✓ invalid filename prints an error
 ✓ empty test file runs zero tests
 ✓ one passing test
 ✓ summary passing tests
 ✓ summary passing and skipping tests
 ✓ summary passing and failing tests
 ✓ summary passing, failing and skipping tests
 ✓ one failing test
 ✓ one failing and one passing test
 ✓ failing test with significant status
 ✓ failing helper function logs the test case's line number
 ✓ test environments are isolated
 ✓ setup is run once before each test
 ✓ teardown is run once after each test, even if it fails
 ✓ setup failure
 ✗ passing test with teardown failure
   (in test file test/bats.bats, line 134)
     `[ "${lines[2]}" = "# (from function \`teardown' in test file $RELATIVE_FIXTURE_ROOT/failing_teardown.bats, line 2)" ]' failed
 ✓ failing test with teardown failure
 ✗ teardown failure with significant status
   (in test file test/bats.bats, line 149)
     `[ "${lines[3]}" = "#   \`eval \"( exit \${STATUS:-1} )\"' failed with status 2" ]' failed
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✓ load aborts if the specified script does not exist
 ✓ load sources scripts by absolute path
 ✓ load aborts if the script, specified by an absolute path, does not exist
 ✓ output is discarded for passing tests and printed for failing tests
 ✓ -c prints the number of tests
 ✓ dash-e is not mangled on beginning of line
 ✓ dos line endings are stripped before testing
 ✓ test file without trailing newline
 ✓ skipped tests
 ✓ extended syntax
 ✓ pretty and tap formats
 ✓ pretty formatter bails on invalid tap
 ✓ single-line tests
 ✓ testing IFS not modified by run
 ✗ executing exported function does not break failing test output
   (in test file test/bats.bats, line 273)
     `[ "${lines[2]}" = "# (in test file test/fixtures/bats/exported_function.bats, line 9)" ]' failed
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✓ running an ad-hoc suite by specifying multiple test files
 ✓ extended syntax in suite

45 tests, 3 failures

Running tests with bash 4.1.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✓ invalid filename prints an error
 ✓ empty test file runs zero tests
 ✓ one passing test
 ✓ summary passing tests
 ✓ summary passing and skipping tests
 ✓ summary passing and failing tests
 ✓ summary passing, failing and skipping tests
 ✓ one failing test
 ✓ one failing and one passing test
 ✓ failing test with significant status
 ✓ failing helper function logs the test case's line number
 ✓ test environments are isolated
 ✓ setup is run once before each test
 ✓ teardown is run once after each test, even if it fails
 ✓ setup failure
 ✓ passing test with teardown failure
 ✓ failing test with teardown failure
 ✓ teardown failure with significant status
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✓ load aborts if the specified script does not exist
 ✓ load sources scripts by absolute path
 ✓ load aborts if the script, specified by an absolute path, does not exist
 ✓ output is discarded for passing tests and printed for failing tests
 ✓ -c prints the number of tests
 ✓ dash-e is not mangled on beginning of line
 ✓ dos line endings are stripped before testing
 ✓ test file without trailing newline
 ✓ skipped tests
 ✓ extended syntax
 ✓ pretty and tap formats
 ✓ pretty formatter bails on invalid tap
 ✓ single-line tests
 ✓ testing IFS not modified by run
 ✗ executing exported function does not break failing test output
   (in test file test/bats.bats, line 273)
     `[ "${lines[2]}" = "# (in test file test/fixtures/bats/exported_function.bats, line 9)" ]' failed
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✓ running an ad-hoc suite by specifying multiple test files
 ✓ extended syntax in suite

45 tests, 1 failure

Running tests with bash 4.2.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✓ invalid filename prints an error
 ✓ empty test file runs zero tests
 ✓ one passing test
 ✓ summary passing tests
 ✓ summary passing and skipping tests
 ✓ summary passing and failing tests
 ✓ summary passing, failing and skipping tests
 ✓ one failing test
 ✓ one failing and one passing test
 ✓ failing test with significant status
 ✓ failing helper function logs the test case's line number
 ✓ test environments are isolated
 ✓ setup is run once before each test
 ✓ teardown is run once after each test, even if it fails
 ✓ setup failure
 ✓ passing test with teardown failure
 ✓ failing test with teardown failure
 ✓ teardown failure with significant status
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✓ load aborts if the specified script does not exist
 ✓ load sources scripts by absolute path
 ✓ load aborts if the script, specified by an absolute path, does not exist
 ✓ output is discarded for passing tests and printed for failing tests
 ✓ -c prints the number of tests
 ✓ dash-e is not mangled on beginning of line
 ✓ dos line endings are stripped before testing
 ✓ test file without trailing newline
 ✓ skipped tests
 ✓ extended syntax
 ✓ pretty and tap formats
 ✓ pretty formatter bails on invalid tap
 ✓ single-line tests
 ✓ testing IFS not modified by run
 ✗ executing exported function does not break failing test output
   (in test file test/bats.bats, line 273)
     `[ "${lines[2]}" = "# (in test file test/fixtures/bats/exported_function.bats, line 9)" ]' failed
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✓ running an ad-hoc suite by specifying multiple test files
 ✓ extended syntax in suite

45 tests, 1 failure

Running tests with bash 4.3.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✓ invalid filename prints an error
 ✓ empty test file runs zero tests
 ✓ one passing test
 ✓ summary passing tests
 ✓ summary passing and skipping tests
 ✓ summary passing and failing tests
 ✓ summary passing, failing and skipping tests
 ✓ one failing test
 ✓ one failing and one passing test
 ✓ failing test with significant status
 ✓ failing helper function logs the test case's line number
 ✓ test environments are isolated
 ✓ setup is run once before each test
 ✓ teardown is run once after each test, even if it fails
 ✓ setup failure
 ✓ passing test with teardown failure
 ✓ failing test with teardown failure
 ✓ teardown failure with significant status
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✓ load aborts if the specified script does not exist
 ✓ load sources scripts by absolute path
 ✓ load aborts if the script, specified by an absolute path, does not exist
 ✓ output is discarded for passing tests and printed for failing tests
 ✓ -c prints the number of tests
 ✓ dash-e is not mangled on beginning of line
 ✓ dos line endings are stripped before testing
 ✓ test file without trailing newline
 ✓ skipped tests
 ✓ extended syntax
 ✓ pretty and tap formats
 ✓ pretty formatter bails on invalid tap
 ✓ single-line tests
 ✓ testing IFS not modified by run
 ✗ executing exported function does not break failing test output
   (in test file test/bats.bats, line 273)
     `[ "${lines[2]}" = "# (in test file test/fixtures/bats/exported_function.bats, line 9)" ]' failed
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✓ running an ad-hoc suite by specifying multiple test files
 ✓ extended syntax in suite

45 tests, 1 failure

Running tests with bash 4.4.0(1)-release

 ✓ no arguments prints usage instructions
 ✓ -v and --version print version number
 ✓ -h and --help print help
 ✓ invalid filename prints an error
 ✓ empty test file runs zero tests
 ✓ one passing test
 ✓ summary passing tests
 ✓ summary passing and skipping tests
 ✓ summary passing and failing tests
 ✓ summary passing, failing and skipping tests
 ✓ one failing test
 ✓ one failing and one passing test
 ✓ failing test with significant status
 ✓ failing helper function logs the test case's line number
 ✓ test environments are isolated
 ✓ setup is run once before each test
 ✓ teardown is run once after each test, even if it fails
 ✓ setup failure
 ✓ passing test with teardown failure
 ✓ failing test with teardown failure
 ✓ teardown failure with significant status
 ✓ failing test file outside of BATS_CWD
 ✓ load sources scripts relative to the current test file
 ✓ load aborts if the specified script does not exist
 ✓ load sources scripts by absolute path
 ✓ load aborts if the script, specified by an absolute path, does not exist
 ✓ output is discarded for passing tests and printed for failing tests
 ✓ -c prints the number of tests
 ✓ dash-e is not mangled on beginning of line
 ✓ dos line endings are stripped before testing
 ✓ test file without trailing newline
 ✓ skipped tests
 ✓ extended syntax
 ✓ pretty and tap formats
 ✓ pretty formatter bails on invalid tap
 ✓ single-line tests
 ✓ testing IFS not modified by run
 ✓ executing exported function does not break failing test output
 ✓ running a suite with no test files
 ✓ running a suite with one test file
 ✓ counting tests in a suite
 ✓ aggregated output of multiple tests in a suite
 ✓ a failing test in a suite results in an error exit code
 ✓ running an ad-hoc suite by specifying multiple test files
 ✓ extended syntax in suite

45 tests, 0 failures