From 4166f0a5d4aec7e398989a6b35d71c5a51a06cd8 Mon Sep 17 00:00:00 2001 From: Martin Pitt Date: Thu, 28 May 2020 10:32:17 +0200 Subject: [PATCH] Use cockpit 220's test runner This will format the test output as TAP and thus provide nice log.html output. Closes #320 --- Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index ae129f5..f8bfec0 100644 --- a/Makefile +++ b/Makefile @@ -138,8 +138,9 @@ vm: $(VM_IMAGE) echo $(VM_IMAGE) # run the browser integration tests; skip check for SELinux denials +# this will run all tests/check-* and format them as TAP check: $(NODE_MODULES_TEST) $(VM_IMAGE) test/common - TEST_AUDIT_NO_SELINUX=1 test/check-application + TEST_AUDIT_NO_SELINUX=1 test/common/run-tests # checkout Cockpit's bots for standard test VM images and API to launch them # must be from master, as only that has current and existing images; but testvm.py API is stable @@ -152,7 +153,7 @@ bots: # checkout Cockpit's test API; this has no API stability guarantee, so check out a stable tag # when you start a new project, use the latest release, and update it from time to time test/common: - git fetch --depth=1 https://github.com/cockpit-project/cockpit.git 219 + git fetch --depth=1 https://github.com/cockpit-project/cockpit.git 220 git checkout --force FETCH_HEAD -- test/common git reset test/common