From f27b2417ffda2a02235cffd01cf95b35132737dd Mon Sep 17 00:00:00 2001 From: Saqib Date: Thu, 17 Sep 2026 12:07:32 +0530 Subject: [PATCH] fix: tests/consumer/functional was in no CI job path (#23) consumer-smoke's default (unset-suite) case hardcoded p="tests/consumer/smoke" -- every other explicit suite case already used the broader p="tests/consumer", only this one legacy default narrowed it. The three registration + privacy-consent tests added in #21/PR#20 (tests/consumer/functional/test_con_registration.py) have never executed in CI since, despite the marker filter already correctly widening to "smoke or functional" on workflow_dispatch/ workflow_call -- the path never let pytest see the file at all. Fix: bring the default case's path in line with the rest. Verified via collection, not just by reading: - -m "smoke" against tests/consumer (push/PR shape): 0 functional tests collected -- no change to everyday behaviour. - -m "smoke or functional" (dispatch/call shape): all 4 functional tests collected (the 3 registration tests + the pre-existing login test), where 0 collected before this fix. --- .github/workflows/run-smoke.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/run-smoke.yml b/.github/workflows/run-smoke.yml index c7db088..e158e4d 100644 --- a/.github/workflows/run-smoke.yml +++ b/.github/workflows/run-smoke.yml @@ -156,7 +156,7 @@ jobs: functional) m="functional"; p="tests/consumer" ;; full) m="smoke or functional or regression"; p="tests/consumer" ;; readonly) m="readonly"; p="tests/consumer" ;; - "") p="tests/consumer/smoke" + "") p="tests/consumer" if [[ "$EVENT" == "workflow_dispatch" || "$EVENT" == "workflow_call" ]]; then m="smoke or functional"; else m="smoke"; fi ;; *) echo "::error::Unknown suite '$SUITE'"; exit 1 ;; esac