running-performance-tests

BbgnsurfTech's avatarfrom BbgnsurfTech

Execute load testing, stress testing, and performance benchmarking.Use when performing specialized testing.Trigger with phrases like "run load tests", "test performance", or "benchmark the system".

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 18, 2025
[Testing and QA]

When & Why to Use This Skill

This Claude skill automates the execution of load, stress, and performance testing to ensure software scalability and reliability. It streamlines the entire performance benchmarking lifecycle—from environment configuration and Bash-based test execution to deep result analysis and automated reporting—helping developers identify system bottlenecks before they impact users.

Use Cases

  • Pre-release Load Testing: Simulating high-concurrency traffic to validate that the system meets performance SLAs before a major product launch.
  • Stress Testing and Breakpoint Analysis: Pushing the infrastructure to its limits to identify failure points and evaluate how the system recovers from resource exhaustion.
  • Performance Regression Benchmarking: Integrating with CI/CD workflows to detect any degradation in response times or throughput caused by recent code changes.
  • Infrastructure Optimization: Analyzing resource utilization metrics (CPU, memory, disk) during peak loads to inform scaling strategies and reduce operational costs.
namerunning-performance-tests
version1.0.0
description|
allowed-toolsRead, Write, Edit, Grep, Glob, Bash(test:perf-*)
licenseMIT

Prerequisites

Before using this skill, ensure you have:

  • Test environment configured and accessible
  • Required testing tools and frameworks installed
  • Test data and fixtures prepared
  • Appropriate permissions for test execution
  • Network connectivity if testing external services

Instructions

Step 1: Prepare Test Environment

Set up the testing context:

  1. Use Read tool to examine configuration from {baseDir}/config/
  2. Validate test prerequisites are met
  3. Initialize test framework and load dependencies
  4. Configure test parameters and thresholds

Step 2: Execute Tests

Run the test suite:

  1. Use Bash(test:perf-*) to invoke test framework
  2. Monitor test execution progress
  3. Capture test outputs and metrics
  4. Handle test failures and error conditions

Step 3: Analyze Results

Process test outcomes:

  • Identify passed and failed tests
  • Calculate success rate and performance metrics
  • Detect patterns in failures
  • Generate insights for improvement

Step 4: Generate Report

Document findings in {baseDir}/test-reports/:

  • Test execution summary
  • Detailed failure analysis
  • Performance benchmarks
  • Recommendations for fixes

Output

The skill generates comprehensive test results:

Test Summary

  • Total tests executed
  • Pass/fail counts and percentage
  • Execution time metrics
  • Resource utilization stats

Detailed Results

Each test includes:

  • Test name and identifier
  • Execution status (pass/fail/skip)
  • Actual vs. expected outcomes
  • Error messages and stack traces

Metrics and Analysis

  • Code coverage percentages
  • Performance benchmarks
  • Trend analysis across runs
  • Quality gate compliance status

Error Handling

Common issues and solutions:

Environment Setup Failures

  • Error: Test environment not properly configured
  • Solution: Verify configuration files; check environment variables; ensure dependencies are installed

Test Execution Timeouts

  • Error: Tests exceeded maximum execution time
  • Solution: Increase timeout thresholds; optimize slow tests; parallelize test execution

Resource Exhaustion

  • Error: Insufficient memory or disk space during testing
  • Solution: Clean up temporary files; reduce concurrent test workers; increase resource allocation

Dependency Issues

  • Error: Required services or databases unavailable
  • Solution: Verify service health; check network connectivity; use mocks if services are down

Resources

Testing Tools

  • Industry-standard testing frameworks for your language/platform
  • CI/CD integration guides and plugins
  • Test automation best practices documentation

Best Practices

  • Maintain test isolation and independence
  • Use meaningful test names and descriptions
  • Keep tests fast and focused
  • Implement proper setup and teardown
  • Version control test artifacts
  • Run tests in CI/CD pipelines