skills.rest
Marshall-Hallenbeck
Marshall-HallenbeckCOMMUNITY
Explore all skills by this author →
𝕏@mjhallenbeckGitHub

run-integration-tests

Execute integration test suites across pytest, Jest, Playwright, and Cypress.

5|1|Updated Oct 18, 2019
Search Tags:#automation#testing#integration#pytest#jest#playwright#cypress
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill run-integration-tests-marshall-hallenbeck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-integration-tests
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/run-integration-tests
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill run-integration-tests-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of testing workflows by providing a unified interface to trigger integration-level validation across diverse technology stacks.

Core Features & Use Cases

  • Cross-Framework Detection: Automatically identifies and executes tests for Python (pytest), JavaScript/TypeScript (Jest), and E2E suites (Playwright, Cypress).
  • Scope-Based Execution: Allows targeted testing of specific layers like backend or E2E, or full-suite validation.
  • Safe Execution Strategy: Prioritizes non-destructive, read-only E2E test suites to prevent accidental data mutation in integrated environments.

Quick Start

Execute the run-integration-tests skill with the backend argument to trigger all integration tests for the server-side components.

Frequently Asked Questions about run-integration-tests

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

FAQPage Schema
How do I run integration tests across multiple frameworks like pytest and Jest?▼

You can run integration tests across frameworks by using a skill that auto-detects project-specific test runners and configurations, targeting backend, E2E, and full-stack scenarios to ensure system-wide component compatibility.

Can I target only backend integration tests without triggering E2E suites?▼

Yes, you can target only backend integration tests by executing the skill with the backend argument, allowing scope-based execution that separates server-side components from E2E and full-stack validation suites.

Does this tool work with Playwright and Cypress for E2E integration testing?▼

Yes, it works with Playwright and Cypress for E2E integration testing by identifying JavaScript and TypeScript suites and prioritizing non-destructive, read-only execution to prevent accidental data mutation in integrated environments.

What is the safest way to execute E2E integration tests in integrated environments?▼

The safest way to execute E2E integration tests is by prioritizing non-destructive, read-only test suites, which prevents accidental data mutation and maintains test integrity across integrated environments.

How does environment-aware test execution handle pytest markers and npm scripts?▼

Environment-aware test execution handles pytest markers and npm script conventions by implementing targeted execution strategies that auto-detect project-specific configurations and maintain test integrity across diverse technology stacks.

Related Skills

Explore More Software Engineering Skills→
PaulKinlanPaulKinlan
2

regression-check

Run full test suites and compare results against a baseline to detect regressions.

Community
Intermediate
denisvmediadenisvmedia
4

inventario-e2e

Run and debug Playwright e2e tests against a local Go backend stack.

Community
Advanced
datorresbdatorresb

testing-strategy

Design test suites with pyramid distribution and TDD workflows.

Community
Intermediate
qazuorqazuor

web-app-testing

Automate web-app testing strategies across unit, integration, component, E2E, and accessibility tests.

Community
Intermediate