DataDogDataDog/browser-sdk/.claude/skills/manual-testing/SKILL.md

manual-testing

Skill400 starsChanged 9 months agoApache-2.0View on GitHub

Run a manual test of the current change end-to-end and output reproducible test instructions for the PR "Test instructions" section.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
If you don't have the PR changes in memory, review all commits in the PR to identify what SDK behavior changed and what events/fields need …
line 8
Very specific:
Create sandbox/test-<topic>.html.
line 20
Very specific:
Use yarn dev-server intake --help to find the right selector.
line 53

“Common” is measured: kept by at least 6 in 10 of the 8 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

Step 1: Understand the change

If you don't have the PR changes in memory, review all commits in the PR to identify what SDK behavior changed and what events/fields need to be verified.

Step 2: Start the dev server

The dev server serves the sandbox/ directory and proxies intake requests locally. Use yarn dev-server --help to list all available commands.

yarn dev-server start

Step 3: Create a temporary sandbox page

Create sandbox/test-<topic>.html. See sandbox/index.html for a minimal example. Include only the elements needed to exercise the change. Always use proxy: '/proxy'.

cat > sandbox/test-<topic>.html << 'EOF'
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <title>Test <topic></title>
    <script src="/datadog-rum.js"></script>
    <script>
      DD_RUM.init({ clientToken: 'xxx', applicationId: 'xxx', proxy: '/proxy', trackUserInteractions: true })
    </script>
  </head>
  <body>
    <!-- elements needed to exercise the change -->
  </body>
</html>
EOF

Step 4: Run the test flow

Get the dev server URL from yarn dev-server status. Clear any previous intake data, open the page, interact with it using CSS selectors, flush events by opening a new tab or reloading, then inspect the intake:

yarn dev-server intake clear
agent-browser open <dev-server-url>/test-<topic>.html
agent-browser click '#...'
agent-browser tab new
yarn dev-server intake <selector> | jq '<field>'

Use yarn dev-server intake --help to find the right selector.

To evaluate JavaScript on the page (e.g. to inspect window state set by beforeSend), switch focus back to tab 0 first, then use agent-browser eval:

agent-browser tab 0
agent-browser eval 'window.someValue'

Step 5: Verify the output matches expectations, then present the test instructions

Output a self-contained bash snippet with the exact commands run and the expected output. This goes directly into the PR "Test instructions" section.

Step 6: Clean up

yarn dev-server stop
rm sandbox/test-<topic>.html

Download now (ZIP)

Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
Relaticle/relaticle★ 1.8ksame name
relaticle/relaticle★ 1.8ksame name
mgifford/accessibility-skills★ 48same name
bmad-labs/skills★ 19same name
mejbaurbahar/fagun★ 1same name
mejbaurbahar/software-tester-skills★ 1same name
miovrag/claude-skills★ 1same name
snuffish/dotfiles★ 0same 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.
Used alongsideProjects with it also use bug-reporting.
Other files people use alongside this one.
- miovragSkill
  bug-reporting
  Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, or AI agent scans. The purpose of this skill is to make accessibility errors easier to report accurately, so that developers can reproduce, understand, and fix them without additional back-and-forth. Absolutely always include the required fields (URL, XPath, HTML snippet, WCAG SC, rule ID, severity, frequency) in every report. Under no circumstances file a vague report that omits the failing element, the WCAG criterion, or the steps to reproduce.
  Also in 3 projects that use this
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- .cursor/rules/test-driven-development.mdcCursor rule
- .cursor/rules/unit-test-best-practices.mdcCursor rule
- running-testsSkill
- writing-commits-and-prsSkill

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