Automate unit, integration, and E2E tests in JavaScript/TypeScript projects.
npx skills add https://github.com/hffmnnj/opencode-goopspec --skill testing-hffmnnj
Please help me install this Agent Skill. Skill: testing Source: https://github.com/hffmnnj/opencode-goopspec/tree/main/skills/testing Command: npx skills add https://github.com/hffmnnj/opencode-goopspec --skill testing-hffmnnj
This Skill helps developers reliably validate software behavior by writing and executing tests that catch regressions early.
Create a test scaffold and run tests using your project's preferred tooling (e.g., npm test or yarn test). Adapt configurations for your framework and coverage goals.
High-intent search queries and answers about installing and using this skill.
Unit tests validate individual functions or modules by isolating code and checking expected behavior. Use Jest or similar frameworks to write test cases with assertions, then run them via npm test or yarn test to catch bugs early in development.
Unit tests verify single functions in isolation; integration tests check how modules work together; E2E tests validate entire workflows from user perspective. All three catch different classes of bugs—unit tests find logic errors, integration tests expose interaction issues, and E2E tests confirm real-world functionality.
Test coverage measures how much code your tests execute. Configure your testing framework (Jest, Playwright) to generate coverage reports showing untested lines, then integrate into CI pipelines to enforce minimum thresholds and identify gaps in test suites.
Yes. Jest integrates directly into CI/CD workflows to automate test execution on every commit. Configure your CI system to run npm test or yarn test, parse test results, and block deployments if tests fail—ensuring code quality before production.
Start with unit tests for core logic and edge cases, then add integration tests for feature dependencies, and finally E2E tests for user workflows. This pyramid approach catches regressions quickly while keeping test suites maintainable and fast.
No, but prioritize tests for business logic, public APIs, and error handling. Skip trivial getters or auto-generated code. Use coverage reports to guide decisions and focus efforts where tests prevent the most costly bugs.
carlos-algmsDetect Jest or Vitest and run targeted frontend unit tests.
yoshisadaEnforce an 80% line and branch coverage gate for changed files.
iamsteveholmesIdentify testing frameworks, runners, and configuration files across codebases.
ROYCE-8425Automate Rust unit, integration, async, and property-based testing with TDD.
