Files
lazygit/scripts/run_integration_tests.sh
Stefan HallerandClaude Opus 5.5 cb5c127b55 Write all integration test coverage to LAZYGIT_GOCOVERDIR
If LAZYGIT_GOCOVERDIR is set, run_integration_tests.sh collects the
coverage of the integration tests. Only the lazygit binary writes its
data to that directory, though. The test runner always writes to
/tmp/code_coverage, so the data ends up in two places unless the
variable points there. On CI it always did.

Also, the run fails if the directory doesn't exist yet. With a relative
path, the binary's data goes missing, because the binary runs in the
directory of the test's repo.

Pass the directory to the test runner too, create it if needed, and turn
it into an absolute path.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 12:50:31 +02:00

34 lines
1.5 KiB
Bash
Executable File

#!/bin/sh
echo "Running integration tests with $(git --version)"
# if the LAZYGIT_GOCOVERDIR env var is set, we'll capture code coverage data
if [ -n "$LAZYGIT_GOCOVERDIR" ]; then
# Go expects us to either be running the test binary directly or running `go test`, but because
# we're doing both and because we want to combine coverage data for both, we need to be a little
# hacky. To capture the coverage data for the test runner we pass the test.gocoverdir positional
# arg, but if we do that then the GOCOVERDIR env var (which you typically pass to the test binary) will be overwritten by the test runner. So we're passing LAZYGIT_GOCOVERDIR instead
# and then internally passing that to the test binary as GOCOVERDIR.
#
# Go doesn't create the coverage directory itself. The lazygit binary runs in
# the directory of the test's repo, so it also needs an absolute path.
mkdir -p "$LAZYGIT_GOCOVERDIR"
LAZYGIT_GOCOVERDIR=$(cd "$LAZYGIT_GOCOVERDIR" && pwd)
export LAZYGIT_GOCOVERDIR
go test -timeout 30m -cover -coverpkg=github.com/jesseduffield/lazygit/pkg/... pkg/integration/clients/*.go -args -test.gocoverdir="$LAZYGIT_GOCOVERDIR"
EXITCODE=$?
else
go test -timeout 30m pkg/integration/clients/*.go
EXITCODE=$?
fi
# If per-test timings were collected (LAZYGIT_TEST_TIMING points at the file the
# harness appends to), print them sorted by slowest first so they show up in the
# CI log.
if [ -n "$LAZYGIT_TEST_TIMING" ] && [ -f "$LAZYGIT_TEST_TIMING" ]; then
echo "Test timings (seconds):"
sort -rn "$LAZYGIT_TEST_TIMING"
fi
exit $EXITCODE