Skip to content

test(release): verify all four editorial guide funnels on deployed HTML - #86

Merged
appdevelopsk merged 4 commits into
mainfrom
test/live-growth-guide-audit-20261107
Nov 7, 2026
Merged

appdevelopsk merged 4 commits into
mainfrom
test/live-growth-guide-audit-20261107

Conversation

@appdevelopsk

Copy link
Copy Markdown
Owner

Production verification gap

Existing read-only scripts/check_growth_live.py checks the catalog and five priority app pages, but omits the four editorial guides. PR #84 added 17 first-party FAQ links to guides and #85 standardized their store-outbound events; we need the production smoke to detect missing, stale or partially published guide HTML.

Change

  • Add four guide paths to the HTTP smoke with a 17-app allowlisted baseline (growth may add more apps without failing).

  • Verify an actual canonical link, expected legacy+shared store and detail event names, and each guide card's Google Play button, matching internal support path, app slug and app-specific accessible name. Reject duplicate/incorrect/missing app links, including any new card without a detail link.

  • Extend valid fixtures and add three negative Python cases: missing Instant Judge detail link, missing AI guide download_click, and an extra guide card lacking a support link.

Verification

Direct source review of scripts/check_growth_live.py and scripts/test_growth_live.py completed: 4 guide routes in PATHS, static smoke checks in place, 37 Python test methods in existing suite.

Reproduced the new guide validation block against representative 17-card guide fixtures: 29/29 positive checks passed, and 4 deliberately broken scenarios (missing detail link, missing event, missing new-card link, wrong support target) correctly failed. These are representative fixtures, not production HTTP results or full 37 Python tests against a fresh checkout.

No GitHub Actions, deployment or claim of GA4 delivery/install growth. Owner can run python3 scripts/check_growth_live.py on networked checkout after publishing main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant