Claude Skill

performance-test-jmeter

Use this skill when you need to design JMeter test plans with Thread Groups, samplers, data sets, assertions, timers, CLI runs, and HTML reports; triggers include JMeter performance testing, performance testing, and performance-test-jmeter.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download naodeng-awesome-qa-skills-skills_en_testing-types_performance-test-jmeter-9df700b.zip · 15 KB

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/performance-test-jmeter
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
Git git clone https://github.com/naodeng/awesome-qa-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.

README

performance-test-jmeter (EN)

Skill Overview

Design JMeter test plans with Thread Groups, samplers, data sets, assertions, timers, CLI runs, and HTML reports.

How to Use

  1. Open SKILL.md in this folder and confirm this skill fits your task.
  2. In your AI tool, call @skill performance-test-jmeter, then add your real project context and goal.
  3. If you need a specific output shape, include it directly in your request.

One-Click Install Script

Run from the repository root:

macOS / Linux

bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill performance-test-jmeter

Windows PowerShell

powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill performance-test-jmeter

Skill manifest

JMeter Performance Testing (EN)

Chinese version: See the corresponding Chinese skill.

When to Use

  • Need outputs that should land in a JMeter performance testing workflow.
  • The project already uses JMeter or wants JMeter-ready planning.

Output Format Options

Markdown by default unless the request explicitly asks for another format.

How to Use

  1. Open prompts/performance-test-jmeter.md and use it as the main prompt.
  2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
  3. If the input is incomplete, return a usable first version and mark missing information and assumptions.

Reference Files

  • When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.

  • prompts/performance-test-jmeter.md: main prompt for this skill.

  • references/framework-spec.md: tool-specific structure and coverage notes.

  • references/setup-and-ci.md: setup, execution, and CI notes.

  • examples/sample-context.md: sample request context.

  • scripts/run-tests.sh: lightweight local execution entry point.

Domain Execution Essentials

  1. Confirm project JMeter/JDK/plugins and JMX version. Check TestPlan/ThreadGroup/Sampler and adjacent hashTree structure, variables, and properties. Parseable XML proves structure only, not execution or SLO success.
  2. Standard ThreadGroup controls closed-loop threads. Target RPS needs declared think time/timers, throughput control, or an installed arrival-rate plugin; verify achieved throughput/counts rather than inferring RPS from threads.
  3. Record CSV path, encoding, columns, sharing, recycle/stopThread settings and consumption per thread/loop. For distributed runs check each injector's data/plugins/network and load allocation.
  4. Use non-GUI entry in authorized environments, preserving JTL/logs. Check business assertions, latency/error gates, and CI propagation separately. Missing thresholds are UNKNOWN; HTML reports or exit 0 cannot hide failed samples.

Common Pitfalls

  • Do not use it with vague scope and no context.
  • Do not treat every area as equally important.
  • Do not skip assumptions and missing information.

Best Practices

  • Start from the prompt file, then add only the context that matters.

  • Keep the output risk-driven and executable.

  • If the request is incomplete, return a usable first version and mark gaps.

  • To check DSL/JMX assets and data-consumption boundaries, read evals/fixtures/jmx/README.md; local examples calibrate assets and cannot establish acceptance without project gates.

Files (awesome-qa-skills)
  • agents
    • openai.yaml 455 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 839 B
        Loading…
      • domain-method-regression.yaml 1.5 KB
        Loading…
      • edge-incomplete-input.yaml 744 B
        Loading…
      • edge-scope-boundary.yaml 1 KB
        Loading…
    • fixtures
      • jmx
        • business-oracle.jmx 3.2 KB · in bundle
        • check_jtl.py 971 B
          Loading…
        • orders.csv 17 B · in bundle
        • README.md 1.4 KB
          Loading…
      • check-domain-decisions.sh 95 B
        Loading…
      • check_domain_decisions.py 3.7 KB
        Loading…
      • domain-oracle.json 155 B
        Loading…
    • eval.yaml 656 B
      Loading…
  • examples
    • sample-context.md 460 B
      Loading…
  • output-templates
    • template-markdown.md 156 B
      Loading…
  • prompts
    • performance-test-jmeter.md 2.7 KB
      Loading…
  • references
    • domain-decision-example.md 1.7 KB
      Loading…
    • framework-spec.md 660 B
      Loading…
    • setup-and-ci.md 761 B
      Loading…
  • scripts
    • run-tests.sh 424 B
      Loading…
  • README.md 792 B
    # performance-test-jmeter (EN)
    
    ## Skill Overview
    
    Design JMeter test plans with Thread Groups, samplers, data sets, assertions, timers, CLI runs, and HTML reports.
    
    ## How to Use
    
    1. Open `SKILL.md` in this folder and confirm this skill fits your task.
    2. In your AI tool, call `@skill performance-test-jmeter`, then add your real project context and goal.
    3. If you need a specific output shape, include it directly in your request.
    
    ## One-Click Install Script
    
    Run from the repository root:
    
    ### macOS / Linux
    
    ```bash
    bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill performance-test-jmeter
    ```
    
    ### Windows PowerShell
    
    ```powershell
    powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill performance-test-jmeter
    ```
    
  • SKILL.md 3.3 KB
    ---
    name: performance-test-jmeter
    description: Use this skill when you need to design JMeter test plans with Thread Groups, samplers, data sets, assertions, timers, CLI runs, and HTML reports; triggers include JMeter performance testing, performance testing, and performance-test-jmeter.
    license: PolyForm-Noncommercial-1.0.0
    metadata:
      version: "1.0.0"
      compatibility: ""
      author: "Awesome QA Skills contributors"
      language: "en"
      category: "testing-types"
      source: "https://github.com/naodeng/awesome-qa-skills"
      license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
    ---
    
    # JMeter Performance Testing (EN)
    
    **Chinese version:** See the corresponding Chinese skill.
    
    ## When to Use
    
    - Need outputs that should land in a JMeter performance testing workflow.
    - The project already uses JMeter or wants JMeter-ready planning.
    
    ## Output Format Options
    
    Markdown by default unless the request explicitly asks for another format.
    
    ## How to Use
    
    1. Open `prompts/performance-test-jmeter.md` and use it as the main prompt.
    2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
    3. If the input is incomplete, return a usable first version and mark missing information and assumptions.
    
    ## Reference Files
    
    - When calibrating domain outcomes, valid controls, or evidence gaps, read [references/domain-decision-example.md](references/domain-decision-example.md) for sanitized input, per-item oracles, and reproducible calculations.
    
    - `prompts/performance-test-jmeter.md`: main prompt for this skill.
    - `references/framework-spec.md`: tool-specific structure and coverage notes.
    - `references/setup-and-ci.md`: setup, execution, and CI notes.
    - `examples/sample-context.md`: sample request context.
    - `scripts/run-tests.sh`: lightweight local execution entry point.
    
    ## Domain Execution Essentials
    
    1. Confirm project JMeter/JDK/plugins and JMX version. Check TestPlan/ThreadGroup/Sampler and adjacent hashTree structure, variables, and properties. Parseable XML proves structure only, not execution or SLO success.
    2. Standard ThreadGroup controls closed-loop threads. Target RPS needs declared think time/timers, throughput control, or an installed arrival-rate plugin; verify achieved throughput/counts rather than inferring RPS from threads.
    3. Record CSV path, encoding, columns, sharing, recycle/stopThread settings and consumption per thread/loop. For distributed runs check each injector's data/plugins/network and load allocation.
    4. Use non-GUI entry in authorized environments, preserving JTL/logs. Check business assertions, latency/error gates, and CI propagation separately. Missing thresholds are UNKNOWN; HTML reports or exit 0 cannot hide failed samples.
    
    ## Common Pitfalls
    
    - Do not use it with vague scope and no context.
    - Do not treat every area as equally important.
    - Do not skip assumptions and missing information.
    
    ## Best Practices
    
    - Start from the prompt file, then add only the context that matters.
    - Keep the output risk-driven and executable.
    - If the request is incomplete, return a usable first version and mark gaps.
    
    - To check DSL/JMX assets and data-consumption boundaries, read [evals/fixtures/jmx/README.md](evals/fixtures/jmx/README.md); local examples calibrate assets and cannot establish acceptance without project gates.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.