#!/usr/bin/env bash

bazel_bin=$(which bazelisk 2>/dev/null)
if [[ -z "$bazel_bin" ]]; then
    echo "Warning: bazelisk is not installed; falling back to bazel."
    bazel_bin=bazel
fi

${bazel_bin} test \
      "$@" \
      //polygerrit-ui:karma_test

#!/usr/bin/env bash

bazel_bin=$(which bazelisk 2>/dev/null)
if [[ -z "$bazel_bin" ]]; then
    echo "Warning: bazelisk is not installed; falling back to bazel."
    bazel_bin=bazel
fi

# At least temporarily we want to know what is going on even when all tests are
# passing, so we have a better chance of debugging what happens in CI test runs
# that were supposed to catch test failures, but did not.
${bazel_bin} test \
      "$@" \
      --test_verbose_timeout_warnings \
      --test_output=all \
      //polygerrit-ui:karma_test

Add flags for verbose test output
Add flags for verbose test output

We have recently seen scary CI runs that should have caught test
failures, but didn't. So we want to see all the test output even when
all tests are passing. At least for now. Feel free to revert this
change when you think that problem is gone and you are annoyed by the
verbose output.

Change-Id: Ic549f4fd18872cb073af148b8df0e49b887e98f0
