Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests.
Install Writing Tests
$ npx skills add operately/operately --skill writing-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install operately/operately writing-tests --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/operately/operately.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-tests .claude/skills/writing-tests && 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 "writing-tests" agent skill from https://github.com/operately/operately/tree/main/.agents/skills/writing-tests into .claude/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tests", 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/operately/operately/tree/main/.agents/skills/writing-testsType 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 operately/operately --skill writing-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install operately/operately writing-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/operately/operately.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-tests .agents/skills/writing-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-tests" agent skill from https://github.com/operately/operately/tree/main/.agents/skills/writing-tests into .agents/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tests", 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 operately/operately --skill writing-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install operately/operately writing-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/operately/operately.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-tests .cursor/skills/writing-tests && 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 "writing-tests" agent skill from https://github.com/operately/operately/tree/main/.agents/skills/writing-tests into .cursor/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tests", 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/operately/operately.git --path .agents/skills/writing-tests--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 operately/operately --skill writing-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install operately/operately writing-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/operately/operately.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-tests .gemini/skills/writing-tests && 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 "writing-tests" agent skill from https://github.com/operately/operately/tree/main/.agents/skills/writing-tests into .gemini/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tests", 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 operately/operately writing-testsInstalls 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 operately/operately --skill writing-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/operately/operately.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-tests .github/skills/writing-tests && 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 "writing-tests" agent skill from https://github.com/operately/operately/tree/main/.agents/skills/writing-tests into .github/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tests", 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 operately/operately --skill writing-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install operately/operately writing-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/operately/operately.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-tests .opencode/skills/writing-tests && 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 "writing-tests" agent skill from https://github.com/operately/operately/tree/main/.agents/skills/writing-tests into .opencode/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tests", 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
writing-tests- GitHub stars
- 576
- Token cost
- ~2.7k tokens
- SKILL.md length
- 755 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests.
- Works in 4 steps: Keep (or add) the normal TurboCase… → Add a QuerySpec / MutationSpec with… → Register the module in spec_modules/0 in… → …
- Reviewing tests
- SKILL.md covers Projections rule (required), Running tests, Test types and case modules and External queries and mutations, plus 5 more sections
- Calls make
What it does
Writing Tests is an agent skill from operately/operately. Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Use when adding, renaming, splitting, or reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase or ExternalApi QuerySpec/MutationSpec tests; or running make test / feature tests.
Its SKILL.md is about 2.7k 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. It works with Elixir and Model Context Protocol. The repository describes itself as: The open source company operating system.
When your agent uses it
- Reviewing tests
- Choosing where a test belongs
- Writing Factory/TurboCase/FeatureCase
- ExternalApi QuerySpec/MutationSpec tests
Example prompts
- “/writing-tests”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Keep (or add) the normal TurboCase *_test.exs for behavior/permissions.
- Add a QuerySpec / MutationSpec with setup/1, inputs/1 (optional), and
- Register the module in spec_modules/0 in queries.ex or mutations.ex.
- Run the matching auth_test.exs (targeted), not the whole suite.
What it can do on your machine
Read from SKILL.md and the folder at commit a11131d. 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:
make
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
Writing Tests loads about 2.7k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 755 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:95
` explicitly in the inner command (root `.env` may have empty `CI=`).
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 755 words (~2,659 tokens).
“Canonical guide for where tests live, how to write them, and how to run them. Pairing rules come from .projections.json.”
- name
- writing-tests
Files
Just SKILL.md in .agents/skills/writing-tests of operately/operately.
Open the folder on GitHubat commit a11131d
Compare with similar skills
Writing Tests 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 |
|---|---|---|---|---|---|---|
| Writing Tests this skilloperately/operately | 576 | — | ~2.7k | Automated safety check: Notes | Custom licence | |
| Qwen Code E2E TestingQwenLM/qwen-code | 28k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| E2Ekortix-ai/suna | 20k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| E2EAgentsMesh/AgentsMesh | 2.4k | — | ~629 | Automated safety check: Notes | Custom licence | |
| Debugging Opik E2E Testscomet-ml/opik | 22k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Playwright E2E Testsonyx-dot-app/onyx | 32k | 1 repos | ~2.8k | Automated safety check: Notes | Custom licence |
Similar skills
E2E
kortix-ai/suna
Agentic end-to-end tests with e2e, the e2e runner. An agent skill from kortix-ai/suna.
E2E
AgentsMesh/AgentsMesh
Selects and runs the appropriate AgentsMesh end-to-end suite for Web, Desktop, MCP, or iOS, including worktree-specific environment setup and browser-level verification.
Debugging Opik E2E Tests
comet-ml/opik
Investigates a failed Opik end-to-end test from CI, TestOps or a local run, decides regression versus flake, and proposes a fix without editing tests.
Playwright E2E Tests
onyx-dot-app/onyx
Write and maintain Playwright end-to-end tests for the Onyx application.
Meridian Evidence
rynfar/meridian
Adversarially review Meridian or scrub changes and preserve reproducible E2E, headless, and visual proof for PRs, critical fixes, merges, and releases.
More from operately/operately
All 9 skills in this repoComponents Architecture
operately/operately
Defines where UI components belong in Operately (TurboUI-first).
Ecto Migrations
operately/operately
Rules for Operately schema migrations (app/priv/repo/migrations/) and data migrations (app/lib/operately/data/change.ex).
MCP Tools
operately/operately
Defines how to add Operately MCP tools (API-first wrappers).
Tanstack Query
operately/operately
Operately frontend data fetching with TanStack Query. An agent skill from operately/operately.
Clean Code
operately/operately
Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language.
Help Docs
operately/operately
Discover help documentation work from operately git history.
Related
Works with
Categories
Questions about Writing Tests
What does Writing Tests do?
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Writing Tests is an agent skill from operately/operately.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests.
When should I use Writing Tests?
Writing Tests fits situations like: reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase; externalApi QuerySpec/MutationSpec tests.
How do I install Writing Tests in Claude Code?
Run `npx skills add operately/operately --skill writing-tests -a claude-code`. Or copy the skill folder (.agents/skills/writing-tests in operately/operately) into .claude/skills/writing-tests in your project. Claude Code loads it when a task matches its description.
How do I install Writing Tests in Codex?
Run `npx skills add operately/operately --skill writing-tests -a codex`. Or copy the skill folder (.agents/skills/writing-tests in operately/operately) into .agents/skills/writing-tests in your project. Codex loads it when a task matches its description.
Can I use Writing Tests 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 operately/operately --skill writing-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-tests, .gemini/skills/writing-tests, .github/skills/writing-tests and .opencode/skills/writing-tests in your project.
What does Writing Tests need to run?
Going by SKILL.md and its folder, Writing Tests needs the command-line tools its instructions call (make).
Does Writing Tests 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 Writing Tests safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Writing Tests use?
Writing Tests has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Writing Tests use?
About 2.7k tokens (SKILL.md is roughly 11k 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 Writing Tests?
Skills that share tags, products or a category with Writing Tests: Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars), E2E (kortix-ai/suna, 20k stars), E2E (AgentsMesh/AgentsMesh, 2.4k stars) and Debugging Opik E2E Tests (comet-ml/opik, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Tests?
operately (a GitHub organization) maintains it in operately/operately, which has 576 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: operately/operately on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.