Running tests with bash 3.1.23(2)-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 3.2.57(2)-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.44(2)-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.1.17(2)-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.53(2)-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.48(2)-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.12(2)-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