testing

Name: testing
Availability: InStock
Author: Octodemo

Run backend unit tests and frontend E2E tests before merging code.

3|Updated Feb 28, 2026

Search Tags:#code quality #unit tests #testing #ci/cd #e2e tests #regression

Ready to run

npx skills add https://github.com/octodemo/tailspin-toys --skill testing-octodemo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/octodemo/tailspin-toys/tree/main/.github/skills/testing-guidelines
Command: npx skills add https://github.com/octodemo/tailspin-toys --skill testing-octodemo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides clear guidelines and commands for running and writing tests, ensuring code quality and preventing regressions before merges.

Core Features & Use Cases

Test Execution: Provides commands to run backend unit tests and frontend E2E tests.
Test Writing Guidance: Offers principles for writing effective, maintainable tests.
Pre-Merge Verification: Outlines a checklist to ensure tests pass before code is merged.
Use Case: Before merging a new feature, use this Skill to run all relevant tests and verify that no existing functionality has been broken.

Quick Start

Run the backend unit tests using the provided script.

Frequently Asked Questions about testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run unit tests and E2E tests before merging code changes?▼

Run unit and E2E tests using the provided script commands to verify code changes and prevent regressions. This pre-merge verification ensures that existing functionality remains intact before integration.

What are the principles for writing effective unit tests?▼

Write tests that are deterministic, independent, fast, focused, and descriptive. These testing principles ensure maintainable test suites that accurately validate code quality and prevent regressions.

How do I debug test failures in my CI/CD pipeline?▼

Debug test failures by running the provided test commands locally to reproduce the CI/CD failure. Use the testing guidelines to isolate broken functionality and verify the code changes causing the regression.

Do I need to run unit and E2E tests separately for backend and frontend?▼

Execute backend unit tests and frontend E2E tests separately using distinct script commands. This separation ensures focused, fast, and deterministic test execution for each application layer.

What's the best way to ensure code quality and prevent regressions before a commit?▼

Follow the pre-merge verification checklist to ensure code quality before commits. Run all relevant unit and E2E tests to verify that no existing functionality is broken by recent code changes.