Upstream software project

shunit2

A xUnit based unit testing for Unix shell scripts

About shunit2

A xUnit based unit testing for Unix shell scripts

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.shunit2: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
shunit2
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
LicenseRef-Callaway-LGPLv2
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

shUnit2 is a xUnit unit test framework for Bourne based shell scripts, and it is designed to work in a similar manner to JUnit, PyUnit, etc. If you have ever had the desire to write a unit test for a shell script, shUnit2 can do the job.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package shunit2

    43 (Fedora 43) (Unspecified): A xUnit based unit testing for Unix shell scripts

    2.1.6-30.fc43: noarch

    Source: shunit2

Fedora 44

  1. Package shunit2

    44 (Fedora 44) (Unspecified): A xUnit based unit testing for Unix shell scripts

    2.1.6-31.fc44: noarch

    Source: shunit2

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.