Test Writing Workflow
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions.
Install Backend Testing
$ npx skills add biersoeckli/QuickStack --skill backend-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install biersoeckli/QuickStack backend-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/biersoeckli/QuickStack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/backend-testing .claude/skills/backend-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 "backend-testing" agent skill from https://github.com/biersoeckli/QuickStack/tree/main/.agents/skills/backend-testing into .claude/skills/backend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-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/biersoeckli/QuickStack/tree/main/.agents/skills/backend-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 biersoeckli/QuickStack --skill backend-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install biersoeckli/QuickStack backend-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/biersoeckli/QuickStack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/backend-testing .agents/skills/backend-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 "backend-testing" agent skill from https://github.com/biersoeckli/QuickStack/tree/main/.agents/skills/backend-testing into .agents/skills/backend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-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 biersoeckli/QuickStack --skill backend-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install biersoeckli/QuickStack backend-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/biersoeckli/QuickStack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/backend-testing .cursor/skills/backend-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 "backend-testing" agent skill from https://github.com/biersoeckli/QuickStack/tree/main/.agents/skills/backend-testing into .cursor/skills/backend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-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/biersoeckli/QuickStack.git --path .agents/skills/backend-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 biersoeckli/QuickStack --skill backend-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install biersoeckli/QuickStack backend-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/biersoeckli/QuickStack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/backend-testing .gemini/skills/backend-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 "backend-testing" agent skill from https://github.com/biersoeckli/QuickStack/tree/main/.agents/skills/backend-testing into .gemini/skills/backend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-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 biersoeckli/QuickStack backend-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 biersoeckli/QuickStack --skill backend-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/biersoeckli/QuickStack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/backend-testing .github/skills/backend-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 "backend-testing" agent skill from https://github.com/biersoeckli/QuickStack/tree/main/.agents/skills/backend-testing into .github/skills/backend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-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 biersoeckli/QuickStack --skill backend-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 biersoeckli/QuickStack backend-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/biersoeckli/QuickStack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/backend-testing .opencode/skills/backend-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 "backend-testing" agent skill from https://github.com/biersoeckli/QuickStack/tree/main/.agents/skills/backend-testing into .opencode/skills/backend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-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
backend-testing- GitHub stars
- 362
- Token cost
- ~670 tokens
- SKILL.md length
- 294 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions.
- Works in 6 steps: Pick the right test type: unit,… → Place the file in the correct location… → For unit tests, mock all external… → …
- Editing backend test files under src/server/
- SKILL.md covers Quick Start, Workflow, Unit Tests and Integration Tests, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Backend Testing is an agent skill from biersoeckli/QuickStack. Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions. Use when editing backend test files under src/server/, src/shared/, or src/tests/integration/, or when the user asks for backend test coverage, mocks, Prisma test DB setup, or Kubernetes integration tests.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `REFERENCE.md`).
It sits in Testing & QA, covering Integration testing, Unit testing and ORMs and data access. It works with Prisma, SQLite, Kubernetes and Vitest. The repository describes itself as: Open-source, self-hostable alternative to Vercel, Netlify, Railway and Heroku. Self-host any app on your own servers in minutes. The licence is GPL-3.0.
When your agent uses it
- Editing backend test files under src/server/
- Src/tests/integration/
- The user asks for backend test coverage
- Prisma test DB setup
Example prompts
- “/backend-testing”
Requirements
- Docker
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Pick the right test type: unit, Prisma/SQLite integration, or k3s integration.
- Place the file in the correct location and use the required filename suffix.
- For unit tests, mock all external dependencies and keep the suite isolated.
- For Prisma integration tests, use createPrismaTestContext('label').
- For k3s integration tests, use createK3sTestContext() and mock the Kubernetes adapter before imports.
- Run the smallest relevant test command first, then broaden if needed.
What it can do on your machine
Read from SKILL.md and the folder at commit 67dc6bd. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Backend Testing loads about 670 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 294 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 biersoeckli/QuickStack at commit 67dc6bd, republished under its GPL-3.0 licence (© biersoeckli). 294 words, ~670 tokens.
Download SKILL.mdSave it as
.claude/skills/backend-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- backend-testing
- description
- Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions. Use when editing backend test files under `src/server/`, `src/shared/`, or `src/__tests__/integration/`, or when the user asks for backend test coverage, mocks, Prisma test DB setup, or Kubernetes integration tests.
Backend Testing
Quick Start
Use these defaults for QuickStack backend tests:
- Name unit tests
*.unit.spec.ts. - Name integration tests
*.integration.spec.ts. - Keep unit tests beside the source file.
- Put integration tests in
src/__tests__/integration/mirroring the source path. - Use Vitest globals without importing
describe,it,expect, orvi. - Prefer
@/...imports for app modules.
Workflow
When creating or updating backend tests:
- Pick the right test type: unit, Prisma/SQLite integration, or k3s integration.
- Place the file in the correct location and use the required filename suffix.
- For unit tests, mock all external dependencies and keep the suite isolated.
- For Prisma integration tests, use
createPrismaTestContext('label'). - For k3s integration tests, use
createK3sTestContext()and mock the Kubernetes adapter before imports. - Run the smallest relevant test command first, then broaden if needed.
Unit Tests
- Mock Prisma, Kubernetes, S3, Longhorn, filesystem, network calls, and singleton services.
- Use
vi.mock()andvi.mocked()for typed mocks. - Use
vi.importActual()for partial mocks when needed. - If a module initializes from environment variables at import time, set env first and call
vi.resetModules()before importing it. - Do not hit the real database, filesystem, or Kubernetes from unit tests.
Integration Tests
- Use a real temporary SQLite database file instead of mocks.
- Use
createPrismaTestContext()for DB lifecycle setup and teardown. - Static top-level imports of services are fine with the Prisma test context.
- Use
ctx.getDataAccess().clientfor direct DB assertions. - Run mutating integration suites with
--pool=forksor--no-file-parallelismwhen Prisma singleton state is involved.
K3s Tests
- Use
createK3sTestContext()for real Kubernetes integration coverage. - Mock
@/server/adapter/kubernetes-api.adapterbefore any related imports. - Use
ctx.getClients()for typed Kubernetes clients. - Use
ctx.getKubeConfig()only when raw kubeconfig access is needed. - Expect slower startup and Docker requirements for these suites.
Reference
See REFERENCE.md for exact naming rules, folder structure, code examples, runtime caveats, and test commands.
© biersoeckli, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/backend-testing of biersoeckli/QuickStack.
- SKILL.md
- REFERENCE.md
Open the folder on GitHubat commit 67dc6bd
Compare with similar skills
Backend 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 |
|---|---|---|---|---|---|---|
| Backend Testing this skillbiersoeckli/QuickStack | 362 | — | ~670 | Automated safety check: Pass | GPL-3.0 | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| NIC Testing Patternsnginx/kubernetes-ingress | 5.1k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| OpenROAD Module Test AdderThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~1.8k | Automated safety check: Pass | BSD-3-Clause | |
| Adding LLM MCP ToolsTriliumNext/Trilium | 38k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Designing TestsCloudAI-X/claude-workflow-v2 | 1.4k | 1 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
NIC Testing Patterns
nginx/kubernetes-ingress
Testing conventions for the NGINX Ingress Controller repo: Go table-driven tests, mandatory snapshot regeneration, Helm tests and Python pytest integration tests.
OpenROAD Module Test Adder
The-OpenROAD-Project/OpenROAD
Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.
Adding LLM MCP Tools
TriliumNext/Trilium
A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…
Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
Frontend Testing
Ohh-889/skyroc
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities.
More from biersoeckli/QuickStack
Elysia API Routes
biersoeckli/QuickStack
Create and update QuickStack Elysia REST API routes using the project's established /api/v1 route conventions.
Backend Services
biersoeckli/QuickStack
Create and update QuickStack backend services, adapters, standalone services, and server actions using the project's established singleton, adapter, caching, and error-handling patterns.
Frontend UI Patterns
biersoeckli/QuickStack
Create and update QuickStack frontend pages, React components, forms, dialogs, tables, streaming UI, and Zustand-backed state using the project's established UI conventions.
Related
Works with
Categories
Questions about Backend Testing
What does Backend Testing do?
Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions. Backend Testing is an agent skill from biersoeckli/QuickStack. Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions.
When should I use Backend Testing?
Backend Testing fits situations like: editing backend test files under src/server/; src/tests/integration/; the user asks for backend test coverage; prisma test DB setup.
How do I install Backend Testing in Claude Code?
Run `npx skills add biersoeckli/QuickStack --skill backend-testing -a claude-code`. Or copy the skill folder (.agents/skills/backend-testing in biersoeckli/QuickStack) into .claude/skills/backend-testing in your project. Claude Code loads it when a task matches its description.
How do I install Backend Testing in Codex?
Run `npx skills add biersoeckli/QuickStack --skill backend-testing -a codex`. Or copy the skill folder (.agents/skills/backend-testing in biersoeckli/QuickStack) into .agents/skills/backend-testing in your project. Codex loads it when a task matches its description.
Can I use Backend 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 biersoeckli/QuickStack --skill backend-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/backend-testing, .gemini/skills/backend-testing, .github/skills/backend-testing and .opencode/skills/backend-testing in your project.
What does Backend Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Backend Testing is instructions for the agent only. Our summary lists: Docker.
Does Backend 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 Backend 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 Backend Testing use?
Backend Testing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Backend Testing use?
About 670 tokens (SKILL.md is roughly 2.7k 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 Backend Testing?
Skills that share tags, products or a category with Backend Testing: Test Writing Workflow (iOfficeAI/AionUi, 33k stars), NIC Testing Patterns (nginx/kubernetes-ingress, 5.1k stars), OpenROAD Module Test Adder (The-OpenROAD-Project/OpenROAD, 3.2k stars) and Adding LLM MCP Tools (TriliumNext/Trilium, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Backend Testing?
biersoeckli (a GitHub user) maintains it in biersoeckli/QuickStack, which has 362 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: biersoeckli/QuickStack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.