It is helpful to know the tests that would be executed with a "make check-acceptance" without executing them. Let's introduce a "make list-acceptance" rule for that purpose.
Signed-off-by: Cleber Rosa <cr...@redhat.com> --- tests/Makefile.include | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tests/Makefile.include b/tests/Makefile.include index 2c03256ae8..d1f90572a7 100644 --- a/tests/Makefile.include +++ b/tests/Makefile.include @@ -17,6 +17,7 @@ ifneq ($(filter $(all-check-targets), check-softfloat),) @echo " $(MAKE) check-softfloat Run FPU emulation tests" endif @echo " $(MAKE) check-acceptance Run acceptance (functional) tests for currently configured targets" + @echo " $(MAKE) check-acceptance List acceptance (functional) tests for currently configured targets" @echo @echo " $(MAKE) check-report.tap Generates an aggregated TAP test report" @echo " $(MAKE) check-venv Creates a Python venv for tests" @@ -135,6 +136,13 @@ check-acceptance: check-venv $(TESTS_RESULTS_DIR) get-vm-images $(if $(GITLAB_CI),,--failfast) tests/acceptance, \ "AVOCADO", "tests/acceptance") +list-acceptance: check-venv + $(call quiet-command, \ + $(TESTS_VENV_DIR)/bin/python -m avocado list \ + --filter-by-tags-include-empty --filter-by-tags-include-empty-key \ + $(AVOCADO_TAGS) tests/acceptance, \ + "AVOCADO", "list tests/acceptance") + # Consolidated targets .PHONY: check-block check check-clean get-vm-images -- 2.31.1