Question 1

How do I write a basic unit test with shUnit2?

Accepted Answer

Create a shell script with functions prefixed 'test', like testEquality() { assertEquals 1 1; }, then source shunit2 at the end. Run the script to execute tests, as shown in the Quickstart section.

Question 2

shUnit2 vs bats: which is better for shell testing?

Accepted Answer

shUnit2 excels in cross-shell compatibility and xUnit patterns, while bats is bash-specific with a different syntax. Use shUnit2 for multi-shell projects and bats for pure bash environments.

Question 3

How to generate JUnit XML reports in shUnit2?

Accepted Answer

Run your test script with --output-junit-xml=filename.xml option. This produces XML output compatible with CI tools like CircleCI, detailed in the Advanced Usage section.

Question 4

Can I skip tests conditionally in shUnit2?

Accepted Answer

Yes, use startSkipping() and endSkipping() functions within tests. For example, to skip bash-specific code, check for BASH_VERSION and call startSkipping if absent, as explained in the Test Skipping section.

Question 5

What shells does shUnit2 support?

Accepted Answer

It supports Bourne sh, bash, dash, ksh, mksh, and zsh. Specific versions are listed in Release Notes, with continuous integration on Ubuntu and macOS.

Question 6

How do I handle setup and teardown in shUnit2?

Accepted Answer

Define oneTimeSetUp, setUp, tearDown, and oneTimeTearDown functions in your test script. These are called automatically for environment management before and after tests.

Question 7

Are there known issues with Zsh in shUnit2?

Accepted Answer

Yes, Zsh requires the shwordsplit option. Set it with setopt shwordsplit in the script or use -y flag when invoking zsh, as detailed in the Zsh appendix.

shunit2

What is shunit2?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions