shunit2
shunit2 copied to clipboard
shUnit2 is a xUnit based unit test framework for Bourne based shell scripts.
``` I see that you already have a ticket offering JUnit/XML ( #16 ) and another suggesting TAP ( #8 ). Neither of those formats collects all of the data...
* Output JUnit XML file can be configured * Test suite text name can be configured * Fix some missing quotes & typos This PR implements issue #16 in a...
You can try it and see if you like it. It works for me. There are no unit tests. If you are interested in this change, I'll try to find...
It seems that shunit2 does not work with the -e flag of bash in some cases (but works fine in other). In particular assertNotNull raises an error (no matter if...
I'd like to be able to source a set of unit tests from a higher-level set of unit tests. Something like this: . detect/unit . info/unit . get/unit . set/unit...
[root@]#./test_1.sh -- test_choose_vhost_bind_cpu8 -------------------------------------------------------------------------------------------------------------------------------------------------- test_choose_vhost_bind_cpu8 -------------------------------------------------------------------------------------------------------------------------------------------------- Ran 1 test. OK -------------------------------------------------------------------------------------------------------------------------------------------------- [root@docke]# 想要在执行这个单独的案例的时候能够,答应出来执行结果,类似于/bin/bash -X
Error handling The constants values SHUNIT_TRUE, SHUNIT_FALSE, and SHUNIT_ERROR are returned from nearly every function to indicate the success or failure of the function. Additionally the variable flags_error is filled...
I've added a package file for [(BASH Package Manager)](https://bpkg.sh) to ease installation with BASH packages, projects, as well as stand alone.
The `${_SHUNIT_LINENO_}` call at the start of assert* functions fails if IFS is redefined ```bash #!/usr/bin/env bash function test_SHUNIT_LINENO_bug() { local var=1 PREVIOUS_FIELD_SEPARATOR=$IFS IFS=, assertEquals "$var" "$var" >&2 IFS=$PREVIOUS_FIELD_SEPARATOR }...
I was just wondering, what is the preferred way of doing something like the example below (which doesn't seem to work): ```sh # my_command.test.sh # Test my_command in fact does...