driver-ui-tests

Create and validate JetBrains IDE UI tests with IDE Starter and UI Driver.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and maintaining UI tests for IDEs can be brittle and time-consuming; this skill provides guidelines and infrastructure patterns to build reliable tests using IDE Starter and UI Driver frameworks.

Core Features & Use Cases

  • Test structure guidance: outlines imports, page objects, and test organization for consistent UI tests.
  • Framework integration: demonstrates using IDE Starter, UI Driver, and aJUnit-like test setup with annotations and utilities.
  • Practical examples: includes code patterns for selectors, page objects, and common test actions, enabling rapid test authoring and maintenance.

Quick Start

Create a new UI test project following the Page Object pattern and run it with the IDE Starter/UI Driver toolchain.

Frequently Asked Questions about driver-ui-tests

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

FAQPage Schema
How do I write reliable UI tests for IntelliJ Platform IDEs?

Reliable UI tests for IntelliJ Platform IDEs require using the IDE Starter and UI Driver frameworks to enforce Page Object design, specify imports, and document test structure for consistent automation.

What is the Page Object pattern for IDE UI test automation?

The Page Object pattern for IDE UI test automation structures test code by separating UI selectors and actions into dedicated page classes, enforced by the UI Driver framework to reduce test brittleness and simplify maintenance.

How do I structure JUnit5 UI tests using UI Driver?

Structuring JUnit5 UI tests with UI Driver involves specifying imports for test utilities, applying framework annotations, and organizing test cases with the IDE Starter toolchain to execute actions consistently.

Can I adopt existing TestOps test cases into IDE Starter?

Yes, you can adopt existing TestOps test cases into IDE Starter; the framework provides specific patterns for migrating and validating test cases across IntelliJ Platform products.

Does this UI testing approach work with all JetBrains IDEs?

Yes, this UI testing approach works with all JetBrains IDEs built on the IntelliJ Platform, applying standardized test structure, selectors, and UI Driver utilities across different product environments.

Why are my IntelliJ Platform UI tests brittle and how do I fix them?

IntelliJ Platform UI tests become brittle without structured patterns; fixing them requires adopting the IDE Starter and UI Driver frameworks to enforce Page Object design, standardize selectors, and organize test structure.