Bats Core is a free, open-source testing framework for Bash scripts, aimed at developers and system administrators who want their shell code checked automatically instead of by hand. It appears in our Other Crypto Tools category because blockchain and crypto projects often rely on shell scripts for builds, node setup and deployment, where a small mistake can be costly. The project is released under the MIT license and carries no price.
Before you download it, know that the last code update was in May 2021, more than two years ago as of 2026. The documentation has also moved to the Read the Docs site. Treat Bats Core as a stable but aging tool: it can still be useful, but check the official project pages for current status before building anything important on it.
What Is Bats Core and How Does It Work?
Bats Core runs tests written as plain text files with a .bats extension. Each file contains test blocks, and each block runs a command and checks the result. A test passes when the command produces the expected output or exits with the expected status code, and it fails otherwise.
This approach is useful because the test files look like the shell code they check. You do not need to learn a separate language to describe what a script should do. A test might state that a helper function returns a specific value when given an empty argument, or that a cleanup routine removes a temporary folder.
Running the whole test folder at once gives a clear summary of which behaviors still work after a change. That summary is the core of the workflow: write small checks, run them often, and fix what breaks.
Who Should Consider Bats Core?
Bats Core fits developers who maintain Bash scripts that matter, such as build helpers, installers or deployment routines. If a broken script would stop a release or corrupt a file, automated checks give you a safety net that manual testing cannot match.
System administrators are another natural audience. They often write shell scripts for backups, log rotation and server provisioning, and they rarely have time to retest every edge case after each edit. A small test suite can verify those routines in minutes.
Developers working on crypto and blockchain projects may also find it useful, even though the tool is general-purpose. Node setup scripts, data export helpers and deployment steps are all shell code. Testing them reduces the chance of a bad configuration reaching a live environment.
Practical Use Cases for Shell Script Testing
Consider a backup script that copies files to a second drive every night. A Bats test can create a sample folder, run the script, and confirm that the copy exists and matches the original. If someone later changes a path variable and the copy silently fails, the test fails first.
Another example is a helper that reads a configuration file and returns a value. You can write tests for normal input, missing keys and malformed lines. Each case documents how the script should behave, which also helps teammates understand it.
Tests are also handy when you inherit old scripts. Writing a few checks for the current behavior lets you refactor safely, because any unintended change will show up as a failed test. Keep each test focused on one behavior so that a failure points you directly to the problem.
Key features
Open-source code under the MIT license
Free to use
Purpose-built for Bash
Documentation on Read the Docs
How to install Bats Core on Windows
- 1
Get the official download
Download only from the official website or the project's GitHub Releases page. Avoid mirrors and file-sharing sites, since repackaged installers are a common way for malicious files to spread.
- 2
Check the file
Compare the SHA-256 checksum of the downloaded archive with the value published alongside the release. If a signature is provided, verify it as well. Do not run any file whose hash does not match.
- 3
Choose a Bash environment
Bats Core is a Bash tool, so on Windows you will usually run it from a Bash shell such as Git Bash or Windows Subsystem for Linux. Read the release notes for Windows-specific instructions before you set up your workflow.
- 4
Extract and install
Unpack the archive to a folder you control and follow the installation instructions included with the release. Add the folder containing the bats command to your PATH so you can run it from any directory.
-
Confirm it runs
Open your Bash shell and run bats --version. If the command prints a version number, the installation is working and you can start writing test files.
How to use Bats Core
Bats Core runs tests written as plain text files. Each file contains test blocks that run commands and check the results, so the workflow stays close to the scripts you already write.
- Create a folder for tests, such as tests/, next to your scripts.
- Write a file ending in .bats and add a test block with a descriptive name.
- Inside the block, run the command you want to check and assert the expected output or exit status.
- Run bats tests/ from the terminal to execute every file in the folder.
- Read the pass and fail summary, then fix the script or the test and run again.
- Add the test command to your routine, for example before each commit or release.
Keep tests small and specific. A test that checks one behavior is easier to read and fix than one that checks everything at once. Name each test after the behavior it protects, so a failure tells you what broke without digging through the code.
Pros & cons
- Free and open source under the MIT license
- Purpose-built for testing Bash scripts
- Simple file-based test format that is easy to read
- Source code is available for review and modification
- Documentation is hosted on a dedicated site
- The last code update was in May 2021, so the project is no longer actively developed
- The documentation has moved, and older guides may be outdated
- Windows support is described as likely rather than confirmed for every setup
- Requires a Bash environment, which adds setup work on Windows
- Not a crypto-specific tool despite its category
Is Bats Core safe?
Bats Core is open source, so its code can be inspected, which helps with trust. Still, download it only from the official website or the project's GitHub Releases page, and never from third-party sites that repackage it. Verify the SHA-256 checksum or signature of the file before running it, and compare the hash with the one published with the release.
Note that the last code update was in May 2021, so the project should be considered unmaintained in the usual sense. Check the latest version on the official website and review the source before using it in any important environment. Because the tool runs shell commands, read any test files you did not write yourself before executing them.
- Official source only. Download from github.com/provable-things/bats-core. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Bats Core occupies a narrow niche: it tests Bash scripts. The other entries in this category serve different purposes. IOHK Address Lib is a related library that may contain relevant logic for handling addresses. PSBT Commander is a Rust-based creator for Partially Signed Bitcoin Transactions, built on BDK. PowerShell Algorand Module is a PowerShell module for working with Algorand.
If you need a test runner for shell scripts, Bats Core is the tool that fits. If your goal is building wallet or transaction logic, the other programs are more relevant starting points. Many teams use both kinds of tools, running Bats Core on their helper scripts while relying on specialized software for blockchain operations.
Specifications
- Price
- Free
- Type
- Open source
- License
- MIT
- Latest version
- v1.3.0
- Last update
- 6 May 2021
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/provable-things/bats-core
Frequently asked questions
Yes, Bats Core is free. It is released as open-source software under the MIT license, so you can use and modify it without paying a fee. The permissive license also suits commercial teams that want to run the tool inside internal build pipelines.
Windows support is described as likely rather than confirmed for every setup. In practice, Bats Core is a Bash tool, so most Windows users run it from Git Bash or Windows Subsystem for Linux. Check the release notes on the GitHub Releases page for build details before you commit to a workflow on Windows.
The last code update was in May 2021, so the project has seen no recent development for more than two years as of 2026. It can still run many scripts, but you should not expect new fixes from recent commits. Review the project status and documentation before relying on it for critical testing.
Create a file ending in .bats and add a test block with a descriptive name. Inside the block, run the command you want to check and assert the expected output or exit status. Then run the file from the terminal to see which tests pass. Start with one simple check so the workflow feels familiar.
A Bash test framework checks that shell scripts behave as expected after changes. You write small test cases that run a command and verify its output or exit status. Teams use this to catch broken deployment steps, faulty backup routines or incorrect helper functions before they reach production.
Alternatives are usually other shell testing frameworks or general testing approaches. Programs such as PSBT Commander or the PowerShell Algorand Module serve different purposes and suit wallet or blockchain tasks better than shell script testing. Compare maintenance status, license and platform support before choosing a replacement.
Verdict
Bats Core is a free, MIT-licensed way to bring automated tests to Bash scripts. It suits developers and administrators who maintain shell tooling, including scripts used around crypto and blockchain projects. Its main drawback is age: the last code update came in May 2021, and the documentation has moved. If you need a simple, readable test runner for shell scripts, it is worth evaluating, but plan for limited future updates.