tester
Use when running tests. Shows how to run tests for a single package, including OpenSearch (ddb-os) tests when applicable.
Best use case
tester is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when running tests. Shows how to run tests for a single package, including OpenSearch (ddb-os) tests when applicable.
Teams using tester should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tester/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tester Compares
| Feature / Agent | tester | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when running tests. Shows how to run tests for a single package, including OpenSearch (ddb-os) tests when applicable.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# Running Tests ## DDB-only tests (default) ```bash yarn test packages/<package-name> ``` ## OpenSearch (ddb-os) tests ```bash yarn test:os packages/<package-name> ``` ## Which command to use Determine which commands to run based on the package. Source of truth: the `storageOps` key in each package's `ci.config.json`. ### Packages that need BOTH `yarn test` AND `yarn test:os` These packages have `storageOps: ["ddb", "ddb-os,ddb"]`: - `api-aco` - `api-audit-logs` - `api-file-manager` - `api-file-manager-aco` - `api-headless-cms` - `api-headless-cms-aco` - `api-headless-cms-bulk-actions` - `api-headless-cms-import-export` - `api-mailer` - `api-scheduler` - `api-workflows` - `tasks` - `testing` ### Packages that need ONLY `yarn test:os` (no standalone ddb) These packages have `storageOps: ["ddb-os,ddb"]` (no separate `"ddb"` entry): - `api-dynamodb-to-elasticsearch` - `api-elasticsearch-tasks` - `api-headless-cms-ddb-es` - `api-headless-cms-es-tasks` - `api-opensearch` ### All other packages — `yarn test` only If a package is not listed above, run only `yarn test`. ## Keeping this list up to date If the list seems stale, re-derive it: ```bash # Packages with ddb-os support grep -rl "ddb-os" --include="ci.config.json" packages/ | sort # Then check each file's storageOps to see if "ddb" is also present ```
Related Skills
webiny-v5-to-v6-migration
Migration patterns for converting v5 Webiny code to v6 architecture. Use this skill when migrating existing v5 plugins to v6 features, converting context plugins to DI services, adapting v5 event subscriptions to v6 EventHandlers, or understanding how v5 patterns translate to v6. Targeted at AI agents performing migrations.
webiny-api-permissions
Schema-based permission system for API features. Use this skill when implementing authorization in use cases, defining permission schemas with createPermissionSchema, creating injectable permissions via createPermissionsAbstraction/createPermissionsFeature, checking read/write/delete/publish permissions, handling own-record scoping, or testing permission scenarios. Covers the full pattern from schema definition to use case integration to test matrices.
webiny-admin-permissions
Admin-side permission UI registration and DI-backed permission checking. Use this skill when adding permission controls to the admin UI — schema-based auto-generated forms, injectable permissions via createPermissionsAbstraction/ createPermissionsFeature, typed hooks (createUsePermissions), the HasPermission component (createHasPermission), and the Security.Permissions component props. Covers both simple apps and complex multi-entity permission schemas.
webiny-sdk
Using @webiny/sdk to read and write CMS data from external applications. Use this skill when the developer is building a Next.js, Vue, Node.js, or any external app that needs to fetch or write content to Webiny, set up the SDK, use the Result pattern, list/get/create/update/publish entries, filter and sort queries, use TypeScript generics for type safety, work with the File Manager, or create API keys programmatically. Covers read vs preview mode, the `values` wrapper requirement, correct method names, and the `fields` required parameter.
webiny-project-structure
Webiny project layout, webiny.config.tsx anatomy, and extension registration. Use this skill when the developer asks about folder structure, where custom code goes, how to register extensions, what webiny.config.tsx does, or how the project is organized. Also use when they need to understand the relationship between extensions/, webiny.config.tsx, and the different extension types (Api, Admin, Infra, CLI).
webiny-local-development
Deploying, developing locally, managing environments, and debugging Webiny projects. Use this skill when the developer asks about deployment commands (deploy, destroy, info), local development with watch mode (API or Admin), the Local Lambda Development system, environment management (long-lived vs short-lived, production vs dev modes), build parameters, state files, debugging API/Admin/Infrastructure errors, or the redeploy-after-watch requirement.
webiny-infrastructure-extensions
Modifying AWS infrastructure using Pulumi handlers and declarative Infra components. Use this skill when the developer wants to customize AWS infrastructure, add Pulumi handlers, configure OpenSearch, VPC, resource tags, regions, custom domains, blue-green deployments, environment-conditional config, or manage production vs development infrastructure modes. Covers CorePulumi.Interface, all <Infra.*> declarative components, and <Infra.Env.Is>.
webiny-infra-catalog
Infrastructure — 33 abstractions. Infrastructure extensions.
webiny-extensions-catalog
extensions — 5 abstractions.
webiny-cli-command-catalog
cli/command — 1 abstractions.
webiny-cli-catalog
cli — 2 abstractions.
webiny-api-tenant-manager-catalog
API — Tenant Manager — 2 abstractions. Tenant management event handlers and use cases.