Conversation
|
It still fails with result is test #10 "echo "a\nb"" failed: This happens with or without my pull request. It's compairing the literal "a\nb" (4 letters) with "a |
|
The latest commit ( df02b94 ) should solve the newline problem |
|
I don't see commit df02b94 in this pull request or your repository. Could you recheck if you've pushed it? |
|
It's two days that I wait for github to update the page (via git I see it pushed). Alas, it has finally appeared, you should be able to see it. |
|
hi I have a problem with this assert |
|
It looks like indeed your expected output and the result are different — For future problems, please also open a new ticket instead of amending an |
|
Sorry, my fault, but with the same string still failing test #24 "get_color red" failed: |
assert.sh fail in a couple cases
using assert, if your tested command has as parameter a string with a space separated asterisk then the asterisk will be evaluated by the shell.
using assert, if your tested command has as parameter a string with characters that have a special meaning in printf, printf will output something unexpected
I suspect that in assert_raises$1 <<< $ {3:-}) > /dev/null 2>&1
(eval
should really be written as
(eval "$1" <<< ${3:-}) > /dev/null 2>&1
but I can't produce a test case similar to 1)
p.s.
I couldn't figure out the meaning of "x required to overwrite older results": is it still needed once printf is gone?