starter-kit/test/run
Martin Pitt 5d2840449a Use Cockpit's shared static code checks
These will soon take over ESLint and stylelint, plus they also cover
ruff and other goodies for the Python part. This supersedes the explicit
ruff call.

This is already being used by cockpit-{podman,machines,navigator} etc.
2024-02-07 17:57:56 +01:00

15 lines
457 B
Bash
Executable file

#! /bin/sh
set -eu
# This is the expected entry point for Cockpit CI; will be called without
# arguments but with an appropriate $TEST_OS, and optionally $TEST_SCENARIO
TEST_SCENARIO="${TEST_SCENARIO:-}"
[ "${TEST_SCENARIO}" = "${TEST_SCENARIO##firefox}" ] || export TEST_BROWSER=firefox
export RUN_TESTS_OPTIONS=--track-naughties
# linters are off by default for production builds, but we want to run them in CI
export LINT=1
make codecheck
make check