Add a maintainers script to safely promote high-confidence legacy risk labels from unknown to concrete values, cover it with tests, and regenerate the canonical skill artifacts and plugin copies. This reduces the legacy unknown backlog without forcing noisy classifications that still need manual review.
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
---
|
|
name: javascript-testing-patterns
|
|
description: "Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices."
|
|
risk: safe
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# JavaScript Testing Patterns
|
|
|
|
Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.
|
|
|
|
## Use this skill when
|
|
|
|
- Setting up test infrastructure for new projects
|
|
- Writing unit tests for functions and classes
|
|
- Creating integration tests for APIs and services
|
|
- Implementing end-to-end tests for user flows
|
|
- Mocking external dependencies and APIs
|
|
- Testing React, Vue, or other frontend components
|
|
- Implementing test-driven development (TDD)
|
|
- Setting up continuous testing in CI/CD pipelines
|
|
|
|
## Do not use this skill when
|
|
|
|
- The task is unrelated to javascript testing patterns
|
|
- You need a different domain or tool outside this scope
|
|
|
|
## Instructions
|
|
|
|
- Clarify goals, constraints, and required inputs.
|
|
- Apply relevant best practices and validate outcomes.
|
|
- Provide actionable steps and verification.
|
|
- If detailed examples are required, open `resources/implementation-playbook.md`.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|