shunit2

shunit2 copied to clipboard

Report file

1

Hello, Shunit2 is amazing But I don't find how to request report file generation. Please advise Regards, Arnaud

abourree

Warning "can only `return' from a function or sourced script" when executing in standalone mode (in Bash shell)

1

# Description When shunit2 is executed in *standalone mode* (in Bash shell) and there are failing test cases, there will be a warning message "can only `return' from a function...

JussiPekonen

Proposing use of https://bpkg.sh/ or any other package manager to allow use in systems where multiple shell dependencies may be included just like PHP and composer, node and npm. This...

richard-muvirimi

shunit2 has not been tested with the proper shell (and the current actual test has been failing)

10

`shunit2_misc_test.sh` is tested with the shell that set in the environment variable `$SHELL`. e.g. ```sh # Note: the test script is prefixed with '#' chars so that shUnit2 does not...

ko1nksm

fail fails to fail the test immediately

4

[blob/master/README.md](https://github.com/kward/shunit2/blob/master/README.md) says fail [message] Fails the test immediately. I thus tried the following code. ``` $ cat t.sh #!/bin/bash testA() { fail "A" fail "B" } source shunit2 $ ./t.sh...

gqqnbig

oneTimeTearDown()/tearDown() is being called an additional time at the end of execution

13

I have been pulling master and had functions that were executing within these hooks and saw what seems to be some unintended behavior. Example file as show below: ``` testSomething()...

vtereso

I have been testing some functions that occasionaly call `exit 1`. Those functions stop the execution of the test file. Before stopping, `shunit2` always says `Ran X tests.`, where `X`...

vmaffet

I received the below error when I run ./test_runner after I did some modifications to `shunit2` code #89 what should I do with this error? ``` testIssue54 ASSERT:call to [...

haobug

Make string difference more readable

5

With this patch: ``` assertEquals "deadbeef" "deadbuff" ``` will output like this ``` ASSERT: expected: ---------------^ but was : ```

haobug

``` Not an issue but an enhancement. I noticed that the skip count was displayed, but not which tests were actually skipped. Since some of my tests only occurs in...

GoogleCodeExporter