Implement JavaScript Testing Patterns
Testing strategies for JavaScript/TypeScript apps - unit, integration, end-to-end, component, and CI/CD testing.
Why it matters
Establish robust testing strategies for JavaScript/TypeScript applications. This skill guides the implementation of unit, integration, and end-to-end tests, including mocking and CI/CD integration.
Outcomes
What it gets done
Set up test infrastructure for new projects.
Write unit, integration, and end-to-end tests.
Implement mocking for external dependencies.
Integrate testing into CI/CD pipelines.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-javascript-testing-patterns | bash Overview
JavaScript Testing Patterns
A guide for unit, integration, end-to-end, and component testing in JavaScript/TypeScript, plus mocking dependencies and CI/CD test setup. Use when setting up test infrastructure, writing tests at any level, mocking dependencies, or integrating tests into CI/CD.
What it does
JavaScript Testing Patterns is a guide for implementing robust testing strategies in JavaScript and TypeScript applications using modern testing frameworks and best practices.
When to use - and when NOT to
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, or setting up continuous testing in CI/CD pipelines. It is not for tasks unrelated to JavaScript testing patterns or for work in a different domain or tool outside this scope.
Inputs and outputs
Given a testing task, the skill applies relevant best practices and produces actionable, verifiable testing steps matched to the scenario - unit, integration, end-to-end, component, or CI/CD test setup. Detailed patterns and examples are available in resources/implementation-playbook.md.
Who it's for
JavaScript and TypeScript developers and teams setting up or extending a test suite - unit, integration, end-to-end, component, or CI/CD-integrated - who want a consistent set of testing patterns to apply across scenarios.
FAQ
Common questions
Discussion
Questions & comments ยท 0
Sign In Sign in to leave a comment.