PHPStan integration
PHPStan adopted bashunit for end-to-end tests, leading to standalone assertions, a line-count assertion and fixes for multiline string comparisons.

You can now run assertions standalone, without a test context. This release also adds assert_line_count and fixes multiline string comparisons.
Earlier this week, PHPStan started integrating bashunit in their e2e tests (PR).
They wanted the assertion functions without the bashunit test runner (Issue).
"Basically we want to use the nice assertions syntax of bashunit not to unit tests bash functions, but to end-to-end tests executables."
@ondrejmirtes
bashunit did not support this, so @staabm created a custom script. Working through that integration led us to add native support for standalone assertions.
Their implementation replaces shell checks with assertions:
- [ $(echo "$OUTPUT" | wc -l) -eq 1 ]
- grep 'Method TraitsCachingIssue\\TestClassUsingTrait::doBar() should return stdClass but returns Exception.' <<< "$OUTPUT"
+ ../bashunit -a line_count 1 "$OUTPUT"
+ ../bashunit -a contains 'Method TraitsCachingIssue\TestClassUsingTrait::doBar() should return stdClass but returns Exception.' "$OUTPUT"./bashunit -a|--assert [...args] allows you to call any assertion outside the test runner, which means you can run them standalone.
The integration also exposed a bug in multiline string comparison, which we fixed. @staabm helped add an assertion to check the number of lines in a string.
These changes are available from 0.13 onwards.