Question 1

shpec vs bats for shell script testing?

Accepted Answer

shpec uses a BDD style with describe/it blocks similar to RSpec, while bats is TAP-based and more minimalistic. Choose shpec if you prefer BDD syntax and extensibility, but bats might be better for simpler, TAP-compliant outputs.

Question 2

How to install shpec on Ubuntu?

Accepted Answer

Use the curl command from the README: sh -c "`curl -L https://raw.githubusercontent.com/rylnd/shpec/master/install.sh`". Ensure you have curl installed and run it in a terminal; it downloads and sets up shpec globally.

Question 3

How to write custom matchers in shpec?

Accepted Answer

Create a .sh file in the shpec/matchers/ directory with a function that includes an assert statement. For example, the README's still_alive matcher uses ping and assert equal to validate server responses.

Question 4

Does shpec support parallel test execution?

Accepted Answer

No, shpec does not natively support parallel test execution. Tests run sequentially, so for large test suites, you might need to use external tools or script wrappers to achieve parallelism.

Question 5

How to integrate shpec with Travis CI?

Accepted Answer

Add shpec to your .travis.yml by including the installation command and running shpec as part of the script. The README shows a Travis CI badge, indicating compatibility with standard CI setups.

Question 6

What shells are compatible with shpec?

Accepted Answer

shpec is designed for POSIX-compliant shells like sh, bash, dash, and ksh. However, the README mentions compatibility notes, so check COMPATIBILITY.md for specifics on shell quirks.

shpec

What is shpec?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions