abecms/VisualQ Quality Gates

Run VisualQ quality gates in CI — visual regression, perf budgets, SEO, a11y, security, tracking, and FRT functional tests

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 10, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: abecms/visualq-action@1530808caa68f7b7ed4eb7fb18694b4dc07045ef # v1.1.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
api-keyVisualQ API keyyes
projectVisualQ project slugyes
typeRun type: test, baseline, perf, seo, a11y, security, tracking, or frttest
feature-idsComma-separated FRT feature IDs (only when type=frt)no
scenariosComma-separated scenario labels to testno
waitWait for run completion (true/false)true
api-urlVisualQ API base URLhttps://visualq.ai
browsersComma-separated browsers to test: chromium,firefox,webkitno
environmentEnvironment name or slug to run tests against (e.g. staging, production)no
jira-keyJira issue key to link results to (e.g. PROJ-123)no
perf-budgetsJSON performance budgets, e.g. {"lcp":2500,"cls":0.1,"score":75}no
a11y-budgetsJSON accessibility budgets, e.g. {"minScore":80,"maxCritical":0,"maxNewViolations":0}no
localeOutput language for action logs (en, fr, es, de, it, pt, pt-BR, nl, pl, tr, ru, zh, ja, ko, ar, hi). Auto-detected from LANG/VISUALQ_LOCALE env vars when omitted.no
namedescription
run-idThe VRT run ID
statusRun status: completed or failed
passedNumber of passed scenarios
failedNumber of failed scenarios
frt-failed-stepsNumber of failed FRT steps when type=frt
report-urlURL to the visual report
perf-scorePerformance score (0-100) when type=perf
seo-scoreSEO score (0-100) when type=seo
a11y-scoreAccessibility score (0-100) when type=a11y or when a11y budgets are set
a11y-critical-countCritical accessibility violation count when type=a11y