Repository navigation
ci: count clicks and keystrokes per feature, with a baseline - #298
Merged
Merged
Conversation
A Playwright survey (ci/clicks) drives a fresh Lens from the web installer through setup and 19 features, counting clicks, keys and passkey prompts per feature, module and page. The Clicks workflow fails when a journey takes more than baseline.json. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018XZkebEbpvyi9y3qmDVD8V
…vering button Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018XZkebEbpvyi9y3qmDVD8V
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018XZkebEbpvyi9y3qmDVD8V
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
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.
Requested by Adeel · project thread
Before: nobody knew how many clicks and keystrokes setup or any feature takes, so friction could creep back unnoticed.
After:
make clicks(and the new Clicks workflow) drives a fresh Lens in Chromium from the web installer through setup and 19 features, and reports clicks, keys and passkey prompts per feature, module and page. A journey that gets more expensive, or breaks, turns CI red.Baseline: 56 clicks, 217 keys, 1 passkey across 19 features (setup, install to first answer: 14 clicks, 63 keys, 1 passkey). 56 pages surveyed for reach from Home and controls.
How:
ci/clicks/run.shstarts the API on a temporary database, the built web app, a stand-in OpenAI-compatible model (so the installer and wizard find a local model and the assistant answers) and the web installer with a stand-in install.sh.meter.mjsholds the counting rules (README),journeys.mjsthe journeys,baseline.jsonthe accepted run.Friction it found, for the follow-up PRs: the welcome tour's question lands in Chat unsent; the Import button sits under the floating Ask button at 1400x900; New note doesn't focus the title; the routines list says "on undefined".
🤖 Generated with Claude Code
https://claude.ai/code/session_018XZkebEbpvyi9y3qmDVD8V
Generated by Claude Code