bats-core mit Homebrew, apk, MacPorts, pacman, apt, dnf, Nix, zypper installieren

Projektlinks

• Homepage
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• bats

Projektgeschichte

The original Bats project dates to Sam Stephenson's 2011-2016 copyright era. The current README says bats-core was forked from the original Bats repository on Tuesday, September 19, 2017 at commit 0360811 after development had stalled and write access to the original repository could not be obtained.

bats-core released Bats 1.0.0 on June 8, 2018. That release emphasized compatibility with 0.4.0 while adding Bash compatibility work, Docker support, better Windows and macOS stability, TAP fixes, and major performance improvements.

The original Bats repository was archived read-only by its owner as of April 29, 2021, and the bats-core README identifies bats-core as the community-maintained Bats project.

Adoptionsgeschichte

Bats-core is widely packaged as the practical shell-testing tool for Unix projects. The input metadata lists apk, Homebrew, Debian, Fedora, MacPorts, Nix, Arch, Ubuntu, and zypper packages, while the upstream README points users to GitHub issues, tested pull requests, examples of projects using Bats, and Read the Docs documentation.

The repository page showed about 6.1k stars, roughly 2,004 commits, and 24 releases at enrichment time, with v1.13.0 shown as the latest release on November 7, 2025.

Wie es verwendet wird

A Bats test file is a Bash script with special syntax for test cases. Under the hood, each test is a function with a description, and ordinary shell commands become assertions through exit status and Bash errexit behavior.

Bats is most useful for testing Bash software, but the README explicitly notes it can test any Unix program. That makes it popular for CLI packages, install scripts, dotfiles, shell libraries, and smoke tests around command-line behavior.

Warum Paket-Nerds sich dafür interessieren

bats-core is one of the package-nerd standards for testing shell-facing software because it sits exactly where many package bugs happen: command names, exit statuses, stdout/stderr, file effects, and portable shell behavior.

Its history also matters culturally. It shows a successful community-maintained fork preserving a small but widely depended-on developer tool when the original repository stalled, while keeping compatibility with existing Bats tests.

Because it emits TAP and uses shell syntax, bats-core fits neatly into old and new CI systems, distro packaging tests, and language-agnostic build pipelines without demanding a heavier test framework.

Zeitleiste

• 2011-2016: Original Bats copyright period credited to Sam Stephenson.
• 2017: bats-core fork created from original Bats on September 19.
• 2018: Bats 1.0.0 released on June 8 with compatibility, Docker, stability, and performance improvements.
• 2021: Original Bats repository archived read-only on April 29.
• 2025: Repository page lists v1.13.0 as latest release on November 7.

Related projects

• sstephenson/bats is the original Bats repository.
• The bats-core ecosystem includes helper libraries such as bats-support, bats-assert, bats-file, and bats-detik.
• TAP is the output protocol family that makes Bats results easy to consume in broader test tooling.

Quellen

• https://github.com/bats-core/bats-core
• https://github.com/bats-core/bats-core/releases/tag/v1.0.0
• https://github.com/bats-core/bats-core/releases/tag/v1.11.1
• https://github.com/sstephenson/bats/issues/236
• source_facts.package-manager