How do I install the Author Tests skill?

Run npx skillmds@latest add azure-azure-sdk-for-js/author-tests in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Author Tests safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Author Tests?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Author Tests free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Author Tests?

Azure (@azure-azure-sdk-for-js) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Author Tests by azure-azure-sdk-for-js

Name: Author Tests
Rating: 4.2 (5 reviews)
Author: Azure

Author Tests

Author skipped Vitest spec files for newly added non-beta ai-projects features under test/. Use when new GA (non-beta) classes, methods, or namespaces appear in review/ai-projects-node.api.md and need test coverage. Generates .skip-ped specs with TODO markers so a human can add recordings, then verifies the test sources compile and lint without running live tests.

Azure Updated Sep 10, 2026

File contents

Author tests for new ai-projects GA features

When to Use

After apply-post-emitter-edits has merged in new public API surface AND that surface is not under project.beta.*.
A new GA class, method, or namespace was added that has no test coverage yet under test/.

Inputs

The api-surface diff JSON from the author-samples skill (or recompute via ../author-samples/prompts/diff-api-surface.prompt.md).
Existing test patterns in test/snippets.spec.ts.

Procedure

Run from sdk/ai/ai-projects/.

Step 1: Filter to GA surface only

From the api-surface diff, drop every entry where isBeta === true or where the namespace path matches *.beta.* / Beta*. Beta surface is intentionally not test-covered by this skill.

Step 2: Scaffold spec file(s)

For each remaining feature, generate a Vitest spec at test/<feature>.spec.ts (or extend an existing related spec) using templates/test-skeleton.spec.ts.

Conventions taken from test/snippets.spec.ts:

Imports: it, describe from vitest; AIProjectClient from ../src/index.js; DefaultAzureCredential from @azure/identity; types via import type.
Endpoint from process.env["FOUNDRY_PROJECT_ENDPOINT"], model from process.env["FOUNDRY_MODEL_NAME"].
Prefer it.skip(...) with a TODO(<feature>): unskip after recording added comment for every new test, so the suite stays green until a human captures recordings.

Step 3: Verify compilation and linting

npx tsc -p tsconfig.test.node.json --noEmit
npx eslint test/<new-or-edited-spec>.ts

Pass every new or edited spec path to the same ESLint invocation. If this skill is a documented no-op and no test files changed, skip ESLint. The TypeScript command must still pass.

Do not use npm run test:node as a compilation check. It runs the package's existing live and recorded suites and can stall or fail for service/environment reasons unrelated to the scaffolded tests.

Step 4: Hand off

Done. Next: the update-changelog skill.

Out of scope

This skill does not create recordings (assets.json, _recordings/). Surface to the human if a recording is needed.
This skill does not test beta surface. Beta features live or die by samples + manual verification.

Notes

Watch for cascade renames from apply-post-emitter-edits. If a method on the public surface was renamed (e.g. listSessionFiles → getSessionFiles), the TypeScript check can fail on existing specs that referenced the old name. Patch those call sites as part of this skill. Cross-reference the rename table in ../apply-post-emitter-edits/references/post-emitter-workarounds.md.

---name: author-testsdescription: Author skipped Vitest spec files for newly added non-beta ai-projects features under test/. Use when new GA (non-beta) classes, methods, or namespaces appear in review/ai-projects-node.api.md and need test coverage. Generates .skip-ped specs with TODO markers so a human can add recordings, then verifies the test sources compile and lint without running live tests.---# Author tests for new ai-projects GA features## When to Use- After `apply-post-emitter-edits` has merged in new public API surface AND that surface is **not** under `project.beta.*`.- A new GA class, method, or namespace was added that has no test coverage yet under `test/`.## Inputs- The api-surface diff JSON from the `author-samples` skill (or recompute via [../author-samples/prompts/diff-api-surface.prompt.md](../author-samples/prompts/diff-api-surface.prompt.md)).- Existing test patterns in [test/snippets.spec.ts](../../../test/snippets.spec.ts).## ProcedureRun from `sdk/ai/ai-projects/`.### Step 1: Filter to GA surface onlyFrom the api-surface diff, drop every entry where `isBeta === true` or where the namespace path matches `*.beta.*` / `Beta*`. **Beta surface is intentionally not test-covered by this skill.**### Step 2: Scaffold spec file(s)For each remaining feature, generate a Vitest spec at `test/<feature>.spec.ts` (or extend an existing related spec) using [templates/test-skeleton.spec.ts](./templates/test-skeleton.spec.ts).Conventions taken from `test/snippets.spec.ts`:- Imports: `it`, `describe` from `vitest`; `AIProjectClient` from `../src/index.js`; `DefaultAzureCredential` from `@azure/identity`; types via `import type`.- Endpoint from `process.env["FOUNDRY_PROJECT_ENDPOINT"]`, model from `process.env["FOUNDRY_MODEL_NAME"]`.- Prefer `it.skip(...)` with a `TODO(<feature>): unskip after recording added` comment for every new test, so the suite stays green until a human captures recordings.### Step 3: Verify compilation and linting```powershellnpx tsc -p tsconfig.test.node.json --noEmitnpx eslint test/<new-or-edited-spec>.ts```Pass every new or edited spec path to the same ESLint invocation. If this skill is a documented no-op and no test files changed, skip ESLint. The TypeScript command must still pass.Do not use `npm run test:node` as a compilation check. It runs the package's existing live and recorded suites and can stall or fail for service/environment reasons unrelated to the scaffolded tests.### Step 4: Hand offDone. Next: the `update-changelog` skill.## Out of scope- This skill **does not** create recordings (`assets.json`, `_recordings/`). Surface to the human if a recording is needed.- This skill **does not** test beta surface. Beta features live or die by samples + manual verification.## Notes- **Watch for cascade renames from `apply-post-emitter-edits`.** If a method on the public surface was renamed (e.g. `listSessionFiles` → `getSessionFiles`), the TypeScript check can fail on existing specs that referenced the old name. Patch those call sites as part of this skill. Cross-reference the rename table in [../apply-post-emitter-edits/references/post-emitter-workarounds.md](../apply-post-emitter-edits/references/post-emitter-workarounds.md).

Frequently asked questions