Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Add or run tests in this repository. An agent skill from s3s-project/s3s.
Install Testing
$ npx skills add s3s-project/s3s --skill testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install s3s-project/s3s testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing .claude/skills/testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "testing" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/s3s-project/s3s/tree/main/.agents/skills/testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add s3s-project/s3s --skill testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install s3s-project/s3s testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/testing .agents/skills/testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add s3s-project/s3s --skill testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install s3s-project/s3s testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/testing .cursor/skills/testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "testing" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/s3s-project/s3s.git --path .agents/skills/testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add s3s-project/s3s --skill testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install s3s-project/s3s testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/testing .gemini/skills/testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install s3s-project/s3s testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add s3s-project/s3s --skill testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/testing .github/skills/testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add s3s-project/s3s --skill testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install s3s-project/s3s testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/s3s-project/s3s.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/testing .opencode/skills/testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/s3s-project/s3s/tree/main/.agents/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
testing- GitHub stars
- 311
- Token cost
- ~748 tokens
- SKILL.md length
- 405 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Add or run tests in this repository. An agent skill from s3s-project/s3s.
- Placing a new test
- SKILL.md covers Where a test goes, Running a subset, What a test should assert and Fixtures, plus 3 more sections
- Calls cargo and just
- A test target is not picked up
What it does
Testing is an agent skill from s3s-project/s3s. Add or run tests in this repository. Use when placing a new test, when a test target is not picked up, when the feature sets matter, or when an end-to-end suite is involved.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering End-to-end testing. The licence is Apache-2.0.
When your agent uses it
- Placing a new test
- A test target is not picked up
- The feature sets matter
- An end-to-end suite is involved
Example prompts
- “/testing”
What it can do on your machine
Read from SKILL.md and the folder at commit 1e1c52e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
cargojust
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Testing loads about 748 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 405 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from s3s-project/s3s at commit 1e1c52e, republished under its Apache-2.0 licence (© s3s-project). 405 words, ~748 tokens.
Download SKILL.mdSave it as
.claude/skills/testing/SKILL.md (or your agent's skills folder).- name
- testing
- description
- Add or run tests in this repository. Use when placing a new test, when a test target is not picked up, when the feature sets matter, or when an end-to-end suite is involved.
- license
- Apache-2.0
Testing
Where a test goes
- Unit tests sit beside the code they exercise, in a
#[cfg(test)] mod testsin the same file, with fixtures in a neighbouring directory (for examplecrates/s3s/src/ops/tests/). - Integration tests live under
crates/<crate>/tests/. Two layouts work: one file per target (tests/dto.rsbecomes thedtotarget) and a directory withmain.rs(tests/protocol/main.rsbecomes theprotocoltarget). Cargo discovers both, so a[[test]]declaration is only needed when the defaults are not enough. - This repository declares one when a target needs
harness = false(a custom harness, ass3s-fsdoes for its AWS and OpenDAL suites) orrequired-features(the HTTP/3 suite needshttp3). Reach for a declaration only for those reasons. - Tests for generated code are generated: see the
code-coverageskill before adding one by hand undercrates/s3s/tests/generated/.
Running a subset
cargo test -p <crate>, cargo test -p <crate> --test <target>, and --all-features for the second feature set. just test is the workspace command (--workspace --all-features --all-targets). CI runs it on two toolchains, on the MSRV and on two platforms. Exercise both feature sets before calling a change done: a merged generated file has code behind both.
What a test should assert
Compare whole values, exact strings or exact error variants, so that a wrong implementation fails for the reason the test names. A test that only checks "did not panic", "is not empty" or "returned Ok" cannot fail for the right reason; the verification skill describes the red control that proves a test can fail at all.
Show full SKILL.md (157 more words)Show less
Fixtures
Keep fixtures next to their tests (crates/s3s/tests/fixtures/, crates/s3s/src/ops/tests/fixtures/) unless the generator consumes them, in which case they belong under data/.
Neighbouring suites
Fuzzing lives in its own workspace and has its own skill (fuzz-testing), as does the scheduled mutation sweep (mutation-testing). What follows is the part of the suite that runs like a test.
End-to-end suites
The end-to-end suites are shell scripts under scripts/ (silo, s3s-fs, s3s-proxy, mint, Ceph s3-tests, rclone, boto3) with their instructions in CONTRIBUTING.md. Two of them are gates with expected-failure baselines: cargo run -p xtask -- report mint <log.json> and cargo run -p xtask -- report s3-tests <junit.xml>, which keep the counters and the allow-list of known failures honest. CI runs them behind path filters, so a green pull request does not mean they ran.
The wasm build
crates/s3s-wasm runs the workspace under WebAssembly with its own suite, covered by the wasm-test CI job; it is the cheapest way to catch a platform assumption.
© s3s-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/testing of s3s-project/s3s.
Open the folder on GitHubat commit 1e1c52e
Compare with similar skills
Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Testing this skills3s-project/s3s | 311 | — | ~748 | Automated safety check: Pass | Apache-2.0 | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| Uloop Replay Inputkurotu/VRCQuestTools | 373 | 3 repos | ~615 | Automated safety check: Pass | MIT | |
| Ui4 Convert Testspayloadcms/payload | 45k | — | ~3.5k | Automated safety check: Pass | MIT | |
| E2Estackia/rtp2httpd | 2.2k | — | ~517 | Automated safety check: Pass | GPL-2.0 |
Similar skills
- Official
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
Uloop Replay Input
kurotu/VRCQuestTools
Replay recorded PlayMode keyboard and mouse input. An agent skill from kurotu/VRCQuestTools.
Ui4 Convert Tests
payloadcms/payload
A skill your agent uses when UI changes are complete and e2e tests need updating.
E2E
stackia/rtp2httpd
Write, run, review, or debug rtp2httpd E2E tests and their harness in e2e/ and scripts/run-e2e.sh.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
More from s3s-project/s3s
All 10 skills in this repoCode Coverage
s3s-project/s3s
Measure and grow the line coverage of the s3s crate. An agent skill from s3s-project/s3s.
Gh Stack
s3s-project/s3s
Work with stacked pull requests in this repository using gh stack.
Code Review
s3s-project/s3s
Review a pull request or a proposed change to this repository.
Codegen
s3s-project/s3s
Change generated code in this repository. An agent skill from s3s-project/s3s.
Fuzz Testing
s3s-project/s3s
Add, run or schedule a fuzz target in this repository. An agent skill from s3s-project/s3s.
Mutation Testing
s3s-project/s3s
Run or triage the mutation sweep in this repository. An agent skill from s3s-project/s3s.
Related
Categories
Questions about Testing
What does Testing do?
Add or run tests in this repository. An agent skill from s3s-project/s3s. Testing is an agent skill from s3s-project/s3s. Add or run tests in this repository.
When should I use Testing?
Testing fits situations like: placing a new test; A test target is not picked up; the feature sets matter; an end-to-end suite is involved.
How do I install Testing in Claude Code?
Run `npx skills add s3s-project/s3s --skill testing -a claude-code`. Or copy the skill folder (.agents/skills/testing in s3s-project/s3s) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.
How do I install Testing in Codex?
Run `npx skills add s3s-project/s3s --skill testing -a codex`. Or copy the skill folder (.agents/skills/testing in s3s-project/s3s) into .agents/skills/testing in your project. Codex loads it when a task matches its description.
Can I use Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add s3s-project/s3s --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.
What does Testing need to run?
Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (cargo and just).
Does Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Testing use?
Testing is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Testing use?
About 748 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Testing?
Skills that share tags, products or a category with Testing: Web Application Testing (anthropics/skills, 180k stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Uloop Replay Input (kurotu/VRCQuestTools, 373 stars) and Ui4 Convert Tests (payloadcms/payload, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing?
s3s-project (a GitHub organization) maintains it in s3s-project/s3s, which has 311 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: s3s-project/s3s on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.