skills.rest
neilmovva
neilmovvaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tests

Define testing guidelines and conventions for the Mux codebase.

Updated Feb 24, 2026
Search Tags:#code quality#unit tests#testing#integration tests#jest#playwright#mocking
One-click install
npx skills add https://github.com/neilmovva/mux --skill tests-neilmovva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/neilmovva/mux/tree/main/.mux/skills/tests
Command: npx skills add https://github.com/neilmovva/mux --skill tests-neilmovva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidelines and conventions for testing the Mux codebase, ensuring code quality, reliability, and maintainability through robust testing strategies.

Core Features & Use Cases

  • Testing Doctrine: Defines preferred testing methodologies (integration vs. unit tests) and their placement.
  • Mocking Strategy: Guides when and how to use mocks, particularly for AI interactions.
  • Test Execution: Specifies how and when different test suites (IPC, UI, E2E) should be run.
  • Use Case: A developer needs to understand how to write a new integration test for a backend feature, ensuring it interacts correctly with the IPC layer without relying on mocks.

Quick Start

Follow the testing doctrine to write integration tests for new features.

Frequently Asked Questions about tests

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

FAQPage Schema
What is the difference between integration tests and unit tests for backend code?▼

Unit tests isolate individual logic components, while integration tests validate feature interactions with layers like IPC without relying on mocks to ensure broader code quality and reliability.

How do I write an integration test that interacts with the IPC layer?▼

Write an integration test by following the established testing doctrine, ensuring the new backend feature interacts correctly with the IPC layer without relying on mocks for execution.

When should I use mocking strategies in my test suites?▼

Use mocking strategies primarily for AI interactions during test execution, ensuring isolated evaluation of code quality while adhering to the defined testing guidelines and conventions.

How should IPC, UI, and E2E test suites be executed?▼

Execute IPC, UI, and E2E test suites according to defined testing guidelines, ensuring comprehensive coverage expectations and rigorous code quality validation across the codebase.

Does this testing doctrine work with Jest and Playwright?▼

The testing guidelines establish comprehensive conventions for unit tests, integration tests, and execution environments that align with frameworks like Jest and Playwright to enforce code reliability.

Related Skills

Explore More Software Engineering Skills→
vlad-ryzhkovvlad-ryzhkov
25

repo-scout

Audit Go backend repositories for API endpoints, infrastructure, and test coverage.

Community
Intermediate
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
Kushal9889Kushal9889

husky

Sets up Husky git hooks to automate code quality checks and testing before commits.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

atdd-assistant

Guide Acceptance Test-Driven Development workflows for defining and validating user stories.

Community
Intermediate