agentleFS
Sign inStart free
EndavaEndava/BEEQ/.agents/skills/write-e2e-tests/SKILL.md

write-e2e-tests

Skill162 starsChanged 11 days agoApache-2.0View on GitHub

Write or fix e2e tests for a `bq-*` component with `@stencil/vitest` in browser mode, covering props, slots, events, methods, keyboard, accessibility attributes and CSS. Use when adding coverage or fixing failing e2e tests. For shared utilities use write-unit-tests.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. tldraw/tldraw★ 51ksame name
    2. igorescodro/alkaa★ 1.6ksame name
    3. akunzai/agent-skills★ 5same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read the full testing instructions

    line 19
  2. Very specific:

    Read the component's .tsx file to understand all @Prop(), @Event(), @Method(), and @Listen() members

    line 20
  3. Very specific:

    Check an existing well-tested file for patterns, e.g.

    line 21
  4. Very specific:

    Create packages/beeq/src/components/<name>/__tests__/bq-<name>.e2e.tsx (see the testing instructions for location, imports and conventions).

    line 25
  5. Very specific:

    Start with the baseline tests (should render, should have shadow root).

    line 26
  6. Distinctive:

    Add at least one test for each coverage category that applies to the component, as listed in the testing instructions: props, slots, …

    line 27
  7. Very specific:

    Follow the conventions in the testing instructions for casting, setProps, async stability, attribute matchers and mock cleanup.

    line 28
  8. Distinctive:

    Run the tests (below) and fix failures before finishing.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Write BEEQ E2E Tests

When to Use

  • Adding E2E tests for a new or existing bq-* component
  • Fixing failing E2E tests after a component change
  • Increasing coverage for untested props, events, or interactions

Before You Start

  1. Read the full testing instructions
  2. Read the component's .tsx file to understand all @Prop(), @Event(), @Method(), and @Listen() members
  3. Check an existing well-tested file for patterns, e.g. packages/beeq/src/components/button/__tests__/bq-button.e2e.tsx

Procedure

  1. Create packages/beeq/src/components/<name>/__tests__/bq-<name>.e2e.tsx (see the testing instructions for location, imports and conventions).
  2. Start with the baseline tests (should render, should have shadow root).
  3. Add at least one test for each coverage category that applies to the component, as listed in the testing instructions: props, slots, events, methods, keyboard, state, accessibility and CSS.
  4. Follow the conventions in the testing instructions for casting, setProps, async stability, attribute matchers and mock cleanup.
  5. Run the tests (below) and fix failures before finishing.

Running the Tests

# Run all e2e tests
pnpm exec nx run beeq:e2e

# Run tests for a specific file
pnpm exec nx run beeq:e2e -- bq-<component>.e2e.tsx

# Watch mode
pnpm exec nx run beeq:e2e -- bq-<component>.e2e.tsx --watch

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free