Timothy Messier
f28bcd4aa7
Several of these tests are being skipped in the enos run. This seems to be due to differences in the setup that is performed. When these tests were run manually, `boundary dev` was used which performs some setup of resources automatically. However since enos uses a non-dev controller, a similar setup is performed via the enos modules. Until the discrepancies between the setup can be investigated, this adds a separate CI job to run the tests against `boundary dev`. These tests are all passing, without any being skipped. This test suite can still be useful even if the enos version is fixed, since this test suite will run much faster, and therefore identify failures sooner.
39 lines
751 B
Bash
Executable File
39 lines
751 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
# TERM isn't set automatically in CI so we need to make sure it's always there.
|
|
export TERM=${TERM:=dumb}
|
|
|
|
function die {
|
|
echo $*
|
|
exit -1
|
|
}
|
|
|
|
# error out early if missing a command
|
|
which boundary || die "missing boundary"
|
|
which jq || die "missing jq"
|
|
which bats || die "missing bats"
|
|
which nc || die "missing nc"
|
|
|
|
echo "starting boundary dev in background"
|
|
boundary dev &>/dev/null &
|
|
boundary_pid=$!
|
|
|
|
function cleanup {
|
|
rv=$?
|
|
echo "stopping boundary dev"
|
|
if [[ -n ${boundary_pid} ]]; then
|
|
kill ${boundary_pid}
|
|
fi
|
|
exit $rv
|
|
}
|
|
|
|
trap cleanup EXIT
|
|
|
|
until boundary scopes list; do
|
|
echo 'waiting for boundary to be up'
|
|
sleep 1
|
|
done
|
|
|
|
echo "running bats tests"
|
|
bats -p ./boundary
|