test(e2e): dashboard honesty regression suite (#164/#165 lock-in)#181
Merged
operatoruplift merged 1 commit intomasterfrom Apr 27, 2026
Merged
test(e2e): dashboard honesty regression suite (#164/#165 lock-in)#181operatoruplift merged 1 commit intomasterfrom
operatoruplift merged 1 commit intomasterfrom
Conversation
Locks in the user-specific fabrication fixes that PRs #164/#165 shipped to /app, /notifications, /workflows. If a future PR drifts back toward fake stats, fabricated activity, or zombie "Blackwall" language, CI fails before merge. ## tests/e2e/dashboard-honesty.spec.ts (new) Three scoped specs running against the dashboard-gated routes via the auth-bypass helpers from #151. | Test | Asserts | |---|---| | /app dashboard | "Helpers installed / Chat sessions / Memories saved" labels present, no "12.4K", "47", "Security Threats Blocked", "Gold Agent", "0.0847", "Blackwall", "Uplift Core Online", "Warp Network", "Event Stream", "US-EAST-1" anywhere in the rendered DOM. Activity feed is empty-state OR real notifications, never the old 5-event fake feed. | | /notifications | No "Blackwall: 3 threats", no "CodePilot Pro updated", no "1,247 new documents". | | /workflows | No "142 runs" / "891 runs" hardcoded fake counts. | The test deliberately uses contextual assertions rather than blanket banned-string match because some numerals are legitimate (e.g. "47" on its own can appear elsewhere; what we're banning is "47 Security Threats Blocked" together). ## .github/workflows/ci.yml dashboard-honesty.spec.ts joins consumer-copy + chat-honesty in the hermetic Playwright run. ## Verified - pnpm exec tsc --noEmit: clean - pnpm check: 3 passed, 0 failed - pnpm exec playwright test dashboard-honesty.spec.ts: 3 passed (37s) ## Rollback Single git revert. 2 files.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Locks in the dashboard fabrication fix in CI
PRs #164 (dashboard home), #165 (notifications/workflows/analytics), #166 (agents/[id], CommandBar, AgentProvider, onboarding, integrations), and #167 (
api/dashboard/statszero-fallback) eliminated user-specific fabrication. This PR adds the regression net so future drift fails CI.tests/e2e/dashboard-honesty.spec.ts(new — 3 specs)Three scoped specs running against the dashboard-gated routes via the auth-bypass helpers from #151.
/appdashboard/notifications/workflowsThe test uses contextual assertions rather than blanket banned-string matching because some numerals are legitimate (e.g. "47" on its own elsewhere). What's banned is the pairing — "Security Threats Blocked" + numeric values together.
CI workflow
Adds
dashboard-honesty.spec.tsto the hermetic Playwright list. The CI run now includes:Verified
Net diff
Rollback
Single
git revert.