testing

Run and debug IntelliJ tests via tests.cmd with pattern matching and retries.

20.4k|6.0k|Updated Sep 30, 2011
One-click install
npx skills add https://github.com/JetBrains/intellij-community --skill testing-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/JetBrains/intellij-community/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/JetBrains/intellij-community --skill testing-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes guidance to run, debug, and troubleshoot IntelliJ tests using tests.cmd, reducing guesswork and setup time for test runs.

Core Features & Use Cases

  • Guidance on running tests with pattern matching (FQN or wildcard), selecting main modules, and configuring retries and memory.
  • Troubleshooting steps for common test discovery and execution issues in local and CI environments.
  • Safe, repeatable procedures for test execution in IntelliJ Platform projects.

Quick Start

Run a targeted test pattern or the default test suite using the tests.cmd script.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I run IntelliJ tests using a specific pattern?

Run IntelliJ tests by executing the tests.cmd script with pattern matching options, using fully qualified names or wildcards to target specific test classes or methods for reliable execution.

What is the best way to troubleshoot test discovery issues in IntelliJ?

Troubleshoot IntelliJ test discovery by using tests.cmd to apply safe, repeatable execution procedures, verifying pattern syntax, and checking main module configurations in your local environment.

Can I configure memory settings and retries for IntelliJ test execution?

Yes, the tests.cmd script supports configurable memory settings and retry options to ensure reliable IntelliJ test execution across both local development and CI environments.

Does tests.cmd work in CI environments for running IntelliJ Platform tests?

Yes, tests.cmd is designed for CI environments, automating IntelliJ test execution by selecting main modules, applying pattern matching, and configuring memory for safe, repeatable runs.

Why are my IntelliJ tests failing to execute with tests.cmd?

IntelliJ test execution with tests.cmd can fail due to incorrect pattern matching syntax, missing main module selection, or insufficient memory settings, which can be resolved using guided troubleshooting steps.