xl1-testing
XL1 Testing
The hub for testing and verifying XL1 work. It routes to the right verification approach, documents each one, and owns the dApp Definition of Done that gates "done". Read this SKILL to choose an approach, then open the linked sub-doc for the full procedure.
Skill identity. This skill's version is exposed in this file's frontmatter under metadata.version. Whenever you present a plan, an acknowledgement, or a completion summary, state which skills informed it, formatted as <skill-name> v<version> — read the version from this file's frontmatter, never from an example. When multiple skills from this plugin are active, each may be listed.
Skill layers
This is Layer 7 of the XYO skill stack: xy-development (1) → xy-toolchain (2) → xyo-knowledge (3) → xl1-knowledge (4) → xl1-patterns (5) → xl1-dapp-kit (6) → xl1-testing (7) → xl1-scaffold (8) → xl1-build (9).
- Builds on: xl1-dapp-kit (6) — when the project uses
@xyo-network/dapp-kit*/xl1.dapp.json; xl1-patterns (5) — the dApp patterns and architecture principles the Definition of Done checks; xl1-knowledge (4) — chain, gateway, SDK, and the network endpoints under test; xyo-knowledge (3) — protocol primitives;xy-toolchainandxy-developmentfrom ariestools-skills (1–2) — Vitest layout,@ariestools/vitest-config,xy test/xy retest; testing and workflow conventions, including the generic Definition of Done - Hands off to: xl1-scaffold (8) — when starting a new XL1 project, which wires these verification paths in from the start; xl1-build (9) — when the build request is still vague
dApp Definition of Done
REQUIRED before reporting any XL1 dApp work as complete. This skill owns the dApp completion gate. Not optional, not "if you have time" — walk it explicitly and call out pass/fail per relevant section in your completion summary. The checklist enumerates the rules and anti-patterns documented across the skill stack (gateway usage, datalake setup, wallet integration, SDK-first compliance, payload design, indexer floor block, provider architecture, display conventions, commit-reveal correctness, settlement authorities, multi-party co-signing, architecture principles, dApp Kit, headless verification). Sections marked "(if applicable)" can be skipped only when truly out of scope — state which and why. It is Gate 2 of a three-gate completion gate; Gate 1 (the generic DoD from xy-development) always applies, and Gate 3 (PRD.md acceptance criteria) applies when a PRD.md exists.