Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
Write unit and integration tests for Ts.ED v8 applications with Vitest (Jest as a fallback) - vitest.config with unplugin-swc, PlatformTest.create/invoke/reset from @tsed/platform-http/testing…
$ npx skills add tsedio/tsed --skill tsed-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tsedio/tsed tsed-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/tsedio/tsed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/tsed/skills/tsed-testing .claude/skills/tsed-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 "tsed-testing" agent skill from https://github.com/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-testing into .claude/skills/tsed-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsed-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/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-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 tsedio/tsed --skill tsed-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tsedio/tsed tsed-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tsedio/tsed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/tsed/skills/tsed-testing .agents/skills/tsed-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 "tsed-testing" agent skill from https://github.com/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-testing into .agents/skills/tsed-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsed-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 tsedio/tsed --skill tsed-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tsedio/tsed tsed-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tsedio/tsed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/tsed/skills/tsed-testing .cursor/skills/tsed-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 "tsed-testing" agent skill from https://github.com/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-testing into .cursor/skills/tsed-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsed-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/tsedio/tsed.git --path plugins/tsed/skills/tsed-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 tsedio/tsed --skill tsed-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tsedio/tsed tsed-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tsedio/tsed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/tsed/skills/tsed-testing .gemini/skills/tsed-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 "tsed-testing" agent skill from https://github.com/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-testing into .gemini/skills/tsed-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsed-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 tsedio/tsed tsed-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 tsedio/tsed --skill tsed-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tsedio/tsed.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/tsed/skills/tsed-testing .github/skills/tsed-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 "tsed-testing" agent skill from https://github.com/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-testing into .github/skills/tsed-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsed-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 tsedio/tsed --skill tsed-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 tsedio/tsed tsed-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tsedio/tsed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/tsed/skills/tsed-testing .opencode/skills/tsed-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 "tsed-testing" agent skill from https://github.com/tsedio/tsed/tree/production/plugins/tsed/skills/tsed-testing into .opencode/skills/tsed-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsed-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.
tsed-testingWrite unit and integration tests for Ts.ED v8 applications with Vitest (Jest as a fallback) - vitest.config with unplugin-swc, PlatformTest.create/invoke/reset from @tsed/platform-http/testing…
Tsed Testing is an agent skill from tsedio/tsed. Write unit and integration tests for Ts.ED v8 applications with Vitest (Jest as a fallback) - vitest.config with unplugin-swc, PlatformTest.create/invoke/reset from @tsed/platform-http/testing, provider mocking with {token, use}, inject() in specs, PlatformTest.createRequestContext, and PlatformTest.bootstrap(Server) with SuperTest and PlatformTest.callback(). Use when adding or fixing .spec.ts files for services, controllers, middlewares or interceptors, when injected properties are undefined in tests, or on the…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/recipes.md`).
It sits in Testing & QA, covering Unit testing and Integration testing. It works with Vitest and Jest. The repository describes itself as: :triangularruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cebcc11. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
vitestFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
tsed.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Tsed Testing loads about 2k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 603 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.
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.
The full file from tsedio/tsed at commit cebcc11, republished under its MIT licence (© tsedio). 603 words, ~2,010 tokens.
.claude/skills/tsed-testing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Build every tested class through the Ts.ED test injector. Never instantiate a DI-managed class (service, controller, middleware, interceptor, module) with new in a test: it bypasses injection, scopes, hooks and mocks.
Read the testing recipes for middleware, interceptor, request-context and stubbing examples. Depth: https://tsed.dev/docs/testing.md, https://tsed.dev/tutorials/vitest.md.
Install vitest unplugin-swc @swc/core @vitest/coverage-v8 (and supertest @types/supertest for integration tests). A project generated by tsed-cli already has this.
// vitest.config.mts
import swc from "unplugin-swc";
import {defineConfig} from "vitest/config";
export default defineConfig({
test: {globals: true, root: "./"},
plugins: [
swc.vite({
jsc: {
target: "es2022",
keepClassNames: true,
parser: {syntax: "typescript", decorators: true},
transform: {useDefineForClassFields: false, legacyDecorator: true, decoratorMetadata: true}
}
})
]
});@Inject() property injection resolve to undefined.useDefineForClassFields: false; class fields would overwrite injected properties.ts-jest per https://tsed.dev/tutorials/jest.md. It is unstable with ESM; prefer Vitest for new projects.PlatformTest.create() (steps 3-4). Fast, no HTTP server.PlatformTest.bootstrap(Server) + SuperTest (step 5).import {inject} from "@tsed/di";
import {PlatformTest} from "@tsed/platform-http/testing";
import {afterEach, beforeEach, describe, expect, it} from "vitest";
import {UsersService} from "./UsersService.js";
describe("UsersService", () => {
beforeEach(() => PlatformTest.create());
afterEach(() => PlatformTest.reset());
it("should return the user", async () => {
const service = inject(UsersService);
expect(await service.findById("1")).toEqual({id: "1"});
});
});PlatformTest.create(settings?) accepts any configuration key: PlatformTest.create({features: {beta: true}}) then read it with constant("features.beta").PlatformTest.get(Token) and inject(Token) return the shared instance. PlatformTest.injector is the InjectorService.inject from @tsed/di. @tsed/platform-http/testing only exports PlatformTest and FakeAdapter.DITest from @tsed/di offers the same create, invoke, get, reset.const repository = {findById: vi.fn().mockResolvedValue({id: "1"})};
const service = await PlatformTest.invoke<UsersService>(UsersService, [{token: UsersRepository, use: repository}]);
expect(await service.findById("1")).toEqual({id: "1"});
expect(repository.findById).toHaveBeenCalledWith("1");PlatformTest.invoke(Token, [{token, use}]) builds a fresh instance with local mocks and runs $onInit. Always await it.describe: PlatformTest.create({imports: [{token: UsersRepository, use: repository}]}), then inject(UsersService).imports entries accept use, useClass, useFactory or useAsyncFactory. useValue is ignored there.{token: DbConnection, use: fakeDb}.await PlatformTest.invoke<UsersController>(UsersController, [...]) and call the handler method directly with plain arguments.vi.mock() a class file that the injector must still register.import {PlatformTest} from "@tsed/platform-http/testing";
import SuperTest from "supertest";
import {afterAll, beforeAll, describe, expect, it} from "vitest";
import {Server} from "../Server.js";
import {UsersController} from "./UsersController.js";
describe("UsersController", () => {
beforeAll(PlatformTest.bootstrap(Server, {mount: {"/rest": [UsersController]}}));
afterAll(PlatformTest.reset);
it("should call GET /rest/users/:id", async () => {
const request = SuperTest(PlatformTest.callback());
const response = await request.get("/rest/users/1").expect(200);
expect(response.body).toEqual({id: "1"});
});
});PlatformTest.bootstrap() returns a function; pass it to beforeAll, or call it: await PlatformTest.bootstrap(Server)().@tsed/platform-express (or -koa, -fastify) in Server.ts or in the spec, or pass {adapter: PlatformExpress}.listen: true is passed. The environment is test and the logger level is off by default.@Configuration keys (only mount, scopes, logger are merged). Passing imports drops the Server's own imports.vi.spyOn(PlatformTest.get(UsersService), "findById").mockResolvedValue(...).Point to @tsed/testcontainers-mongo (https://tsed.dev/tutorials/mongoose.md) and the premium @tsedio/testcontainers-* packages (Postgres, Redis, Vault) listed in https://tsed.dev/docs/testing.md. Do not hand-roll container lifecycle code when a package exists.
PlatformTest.bootstrap: no adapter package was imported. Add import "@tsed/platform-express";.beforeEach(PlatformTest.create) passes Vitest's test context as settings. Write beforeEach(() => PlatformTest.create()).PlatformTest.reset leaks providers, hooks and mocks into the next file and keeps handles open.PlatformTest.invoke without await returns a promise; assertions then run on the promise.PlatformTest.inject([Token], cb) is deprecated. Use inject() or PlatformTest.invoke().context() need runInContext(PlatformTest.createRequestContext(), () => ...) from @tsed/di.PlatformTest.bootstrap per file in beforeAll, not beforeEach: bootstrapping the server per test is slow.@tsed/common; PlatformTest lives in @tsed/platform-http/testing.vitest.config uses unplugin-swc with decorators, legacyDecorator, decoratorMetadata and useDefineForClassFields: false.new on a DI-managed class anywhere in the specs; instances come from inject(), PlatformTest.get() or PlatformTest.invoke().PlatformTest.create/bootstrap has a matching PlatformTest.reset.{token, use} and are asserted with toHaveBeenCalledWith; success and error paths are covered.SuperTest(PlatformTest.callback()).© tsedio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in plugins/tsed/skills/tsed-testing of tsedio/tsed.
Open the folder on GitHubat commit cebcc11
Tsed 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 |
|---|---|---|---|---|---|---|
| Tsed Testing this skilltsedio/tsed | 3.1k | — | ~2k | Automated safety check: Pass | MIT | |
| Designing TestsCloudAI-X/claude-workflow-v2 | 1.4k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Test Behavior Not Implementationfmflurry/settings-opencode | 171 | — | ~736 | Automated safety check: Pass | MIT | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Vitestsupabase/supabase | 111k | 12 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Test GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~2.1k | Automated safety check: Pass | MIT |
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
fmflurry/settings-opencode
A skill your agent uses when writing, reviewing, or keeping a unit/integration test (Jest, Vitest, xUnit).
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.
supabase/supabase
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
pixel-point/animate-text
Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest).
tsedio/tsed
Create a production-ready Ts.ED platform adapter for a new HTTP framework or runtime, such as Hono, Elysia, Bun.serve, or a Node framework.
tsedio/tsed
Scaffolds Ts.ED v8 projects and generates files with the Ts.ED CLI v7, through its MCP server (tools set-workspace, init-project, list-templates, get-template, generate-file) or the tsed binary…
tsedio/tsed
Configure and bootstrap a Ts.ED v8 server - the @Configuration decorator or configuration() on the Server class, PlatformExpress/PlatformKoa/PlatformFastify.bootstrap, server options (mount…
tsedio/tsed
Declare, inject and scope Ts.ED v8 providers and wire lifecycle hooks - @Injectable, @Module, @Controller, @Inject, the functional API (inject, injectMany, lazyInject, constant, refValue…
tsedio/tsed
Locates authoritative Ts.ED v8 documentation and API reference instead of guessing framework APIs.
tsedio/tsed
Configure and use logging in a Ts.ED v8 application with @tsed/logger v8.
Categories
Write unit and integration tests for Ts.ED v8 applications with Vitest (Jest as a fallback) - vitest.config with unplugin-swc, PlatformTest.create/invoke/reset from @tsed/platform-http/testing…. Tsed Testing is an agent skill from tsedio/tsed.callback().
Tsed Testing fits situations like: fixing .spec.ts files for services; injected properties are undefined in tests; on the error Platform type is not specified / a missing platform adapter.
Run `npx skills add tsedio/tsed --skill tsed-testing -a claude-code`. Or copy the skill folder (plugins/tsed/skills/tsed-testing in tsedio/tsed) into .claude/skills/tsed-testing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add tsedio/tsed --skill tsed-testing -a codex`. Or copy the skill folder (plugins/tsed/skills/tsed-testing in tsedio/tsed) into .agents/skills/tsed-testing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tsedio/tsed --skill tsed-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/tsed-testing, .gemini/skills/tsed-testing, .github/skills/tsed-testing and .opencode/skills/tsed-testing in your project.
Going by SKILL.md and its folder, Tsed Testing needs the command-line tools its instructions call (vitest).
SKILL.md names 1 domain. In commands or code: tsed.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Tsed Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Tsed Testing: Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), Test Behavior Not Implementation (fmflurry/settings-opencode, 171 stars), Test Writing Workflow (iOfficeAI/AionUi, 33k stars) and Vitest (supabase/supabase, 111k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
tsedio (a GitHub organization) maintains it in tsedio/tsed, which has 3,088 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: tsedio/tsed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.