Skip to content

docs(testing): CV-default Mobile testing layers - #70

Merged
racitores merged 3 commits into
mainfrom
raci/cv-skill-update-development
Jul 22, 2026
Merged

racitores merged 3 commits into
mainfrom
raci/cv-skill-update-development

Conversation

@racitores

@racitores racitores commented Jul 20, 2026 •

Copy link
Copy Markdown
Contributor

Description

Make component-view the default MetaMask Mobile test layer for screen/view UI behavior, with unit as a focused fallback and e2e for device journeys.

  • Add canonical policy: domains/testing/knowledge/testing-layers.md (installed beside testing skills)
  • Align Mobile overlays for coding-guidelines, unit-testing, component-view-test, pr-guidelines, and pr-readiness-check
  • Document CV and unit as peer skills (same entry structure / discovery); stop implying unit-testing is the primary testing guide
  • Point Perps review antipatterns / perps-review-pr at the shared layers policy (keep Perps-specific path enforcement)
  • README discovery examples install/describe CV + unit together
  • Policy wording uses Appium for device E2E (not Detox); full e2e-test skill migration is out of scope

Some more context about the reason:
https://kentcdodds.com/blog/the-testing-trophy-and-testing-classifications (creator of testing-library)
https://x.com/swyx/status/1261202288476971008

Type of Change

  • New skill
  • Skill improvement/update
  • Bug fix
  • Documentation update
  • Other (please describe):

Skill Details (if adding a new skill)

Provider Name:
Skill Name:
Brief Description:

Checklist

  • I have read the CONTRIBUTING.md guidelines
  • My skill follows the SKILL_TEMPLATE.md format
  • I have tested this skill with an AI agent
  • My skill does not contain any secrets, private keys, or sensitive data
  • I have added appropriate documentation
  • My changes don't break existing skills

Testing

  • Reviewed layered guidance across updated Mobile skills for consistency (CV default → unit fallback → e2e)
  • Confirmed installer already copies domains/testing/knowledge/ beside testing-domain skills (copy_domain_knowledge)
  • No runtime/code changes; documentation/skills only

Additional Context

Mobile-only. Extension overlays unchanged. The detailed Detox→Appium rewrite of e2e-test remains a follow-up.

Made with Cursor

Add shared testing-layers policy and align Mobile coding, PR, unit, and
CV skills so agents prefer *.view.test.tsx and use unit tests as fallback.

Co-authored-by: Cursor <cursoragent@cursor.com>
Comment thread domains/testing/knowledge/testing-layers.md Outdated
Co-authored-by: João Tavares <joao.tavares@consensys.net>
@racitores

racitores commented Jul 22, 2026 •

Copy link
Copy Markdown
Contributor Author

Thanks for the linked resources in the PR description suggestion @cryptotavares!

@racitores
racitores enabled auto-merge (squash) July 22, 2026 13:31
@racitores
racitores merged commit cf424ca into main Jul 22, 2026
27 checks passed
@racitores
racitores deleted the raci/cv-skill-update-development branch July 22, 2026 14:49
racitores added a commit that referenced this pull request Jul 27, 2026
Extend the CV-default guidance from #70 across coding, PR-workflow, and perps review skills so app-to-controller flows are steered to the integration layer under the best-fit-layer model.

Co-authored-by: Cursor <cursoragent@cursor.com>
andrepimenta added a commit that referenced this pull request Sep 7, 2026
Step 2 of docs/processes/releasing.md — "review the generated CHANGELOG.md
section and keep entries consumer-facing". The generated section needed it in
two places.

`### Uncategorized` held ten merged PRs that never got a hand-written entry.
Since `package.json` `files` ships `domains/` alongside `bin/` and `tools/`,
skill content reaches consumers on upgrade, so most of these are genuinely
user-facing and belong in the notes rather than being dropped. Rewritten from
the consumer's point of view and grouped by theme rather than one line per PR:
the component-view testing work (#109, #115, #132) reads as one change, as does
the Mobile testing default plus the Appium playbook move (#70, #54).

Dropped #63 and #77 — `.cursor` review rules and `.github`/`CONTRIBUTING`
changes are not in the published package, so an upgrading consumer sees nothing
of them.

`### Added` had the same problem less visibly: around a dozen raw
conventional-commit titles (`feat: add ...`, `feat(cli): ...`) that read as
commit log rather than release notes. Prefixes stripped, past tense applied.
Three were duplicates of curated entries for the same PR (#136, #75, and the
component-view flakiness line now covered by the #109 entry) and were removed.

Verified: `lint:changelog` passes, 69/69 tests, lint clean, `pack:dry-run` ok.
No `Uncategorized` section and no conventional-commit prefixes remain.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

3 participants