tests/cli/test_trace_read: use `bt_cli` and `isnt`

This makes the output more readable/analyzable on failure.

Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Change-Id: I6bb7d76538c843a50e605756493de0755cc9ca11

diff --git a/tests/cli/test_trace_read b/tests/cli/test_trace_read
index b3a30a7eac38fef992919d8a0856dfb24679cdb7..f8c560be923661848b550f0a43e16fb5d87e8b98 100755 (executable)
--- a/tests/cli/test_trace_read
+++ b/tests/cli/test_trace_read
@@ -25,15 +25,12 @@ plan_tests $NUM_TESTS
 
 for path in "${SUCCESS_TRACES[@]}"; do
        trace=$(basename "${path}")
-       "${BT_TESTS_BT2_BIN}" "${path}" > /dev/null 2>&1
+       bt_cli /dev/null /dev/null "${path}"
        ok $? "Run babeltrace2 with trace ${trace}"
 done
 
 for path in "${FAIL_TRACES[@]}"; do
        trace=$(basename "${path}")
-       if "${BT_TESTS_BT2_BIN}" "${path}" > /dev/null 2>&1; then
-               fail "Run babeltrace2 with invalid trace ${trace}"
-       else
-               pass "Run babeltrace2 with invalid trace ${trace}"
-       fi
+       bt_cli /dev/null /dev/null "${path}"
+       isnt "$?" 0 "Run babeltrace2 with invalid trace ${trace}"
 done