weird behaviour for piped commands

[pkeroulas]

Intuitively, I wanted to check if cukinia supports piped commands.

This sequence

as grep cukinia_cmd echo toto | grep toto
as cat  cukinia_cmd echo toto | cat 
as awk  cukinia_cmd echo toto | awk '/toto/'
as wc   cukinia_cmd echo toto | wc
as sed  cukinia_cmd echo toto | sed 's/o/i/g'
cukinia_log "$cukinia_tests"

gives:

[PASS] cat
        1         2        21
[PASS] sed
0

It looks like something, probablyecho toto, is executed because of PASS but the result is ignored (cukinia_test==0). So, the output is confusing because cat and sed look fine. And it's not clear why some commands ouput something while other don't.

Quoting the expression ("cmd1|cmd2") helps cukinia_test incrementing but always returns FAIL regardless of cmd1 and cmd2.

The use of "|" in the syntax should be either forbidden by documentation either fixed somehow.

[joufella]

The cukinia config file is just a shell script, so when you do:

as "my test" cukinia_cmd echo toto | grep toto

The following happens:

• as "my test" cukinia_cmd echo toto is executed
• this command produces the output [PASS] my test
• this output is piped into grep toto
• toto is not present on the line, so nothing is displayed.

The 1 2 21 output is normal piping the same type of string into wc.

For more complex tests like that, you should use

# complex test scenario
cat /myfile | sed -e 'some magic' | grep -q 'some result'
as "this complex scenario" cukinia_test $? -eq 0