| AArch64 | |
| ppc64le | |
| s390x | |
| x86-64 |
- update to 1.1.0 - drop build-term.patch package-json.patch - new upstream, see changes on https://github.com/bats-core/bats-core/releases
- Added build-term.patch: work-around for bnc#1026350
- Fix RPM group
- Spec file improvements: * Run tests in %check section * Correct project URL
- Spec file improvements: * /usr/bin/tput is optional at runtime * Reference to meaning of TAP-compliant * Simplify launch of tests
- Initial version: bats 0.4.0
- update to 1.10.0:
* add `${BATS_TEST_TAGS[@]}` for querying the tags during a
test
* print tags on failing tests
* test for negative arguments to `--jobs`
* add tests for `--formatter cat`
* test coverage in CI
* Support for rush as alternative to GNU parallel
* add `bats_pipe` helper function for `run` that executes `\|`
as pipes
* publish docker images to ghcr.io (additionally to Dockerhub)
* clarify use cases of `--formatter cat`
* fix `run` with options overwriting the value of `i`
* fix `${BATS_TEST_NAMES[@]}` containing only `--tags` instead
of test name since Bats v1.8.0
* fix `run --keep-empty-lines` counting trailing ` ` as
(empty) new line
* fix short flag unpacker creating bogus command lines with
valued flags
* fix formatter becoming confused with retries
* fix `--gather-test-outputs-in` fails on tests with `/`
* fix overriding `date` breaks `--timing`
- Update to version 1.9.0:
* add installation instructions for Debian, Fedora, Gentoo, and OpenSUSE (#659)
* add `--line-reference-format` to switch file/line references in stack traces (#665)
* add `bats:focus` tag to run only focused tests (#679)
* add bats-support, bats-assert, bats-file and bats-detik to Dockerfile (#674)
* add `--help` text and `man` page content for `--filter-tags` (#679)
* explicitly check for GNU parallel (#691)
* wait for report-formatter to finish before ending `bats`' execution,
to fix empty files with `--report-fomatter junit` under Docker (#692)
* improved clarity of section about output in free code (#671)
* fixed typos (#673)
* clarify use cases of `run` (#366)