Added --configuration-cache flag to buildPlugin task in all Linux
UI test workflows to significantly improve build performance.
The configuration cache stores the result of the configuration phase
and reuses it for subsequent builds, avoiding the need to re-evaluate
build scripts when inputs haven't changed. This is particularly
beneficial for UI tests that run frequently on schedule.
Note on "Gradle User Home cache not found" message: This is expected
when the commit SHA changes, as the gradle-home cache key includes it
for security. However, the more important dependency and transform
caches use content-based hashing and are restored correctly across
commits, which is why builds still benefit from caching.
Updated workflows:
- runUiTestsLinux.yml
- runUiRdTestsLinux.yml
- runUiPyTestsLinux.yml
- runUiTestsUnified.yml (both jobs)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Added explicit instruction to all UI test failure analysis prompts:
"IMPORTANT: If you have a concrete suggestion for fixing the test,
ALWAYS proceed with creating a branch and PR. Never ask for
permission - just do it."
This ensures Claude Code will automatically create fix PRs when it
identifies concrete solutions, eliminating the need for user
confirmation and enabling fully automated test maintenance.
Updated workflows:
- runUiTests.yml (IntelliJ macOS)
- runUiTestsLinux.yml (IntelliJ Linux)
- runUiTestsUnified.yml (IntelliJ unified)
- runUiRdTests.yml (Rider macOS)
- runUiRdTestsLinux.yml (Rider Linux)
- runUiPyTests.yml (PyCharm macOS)
- runUiPyTestsLinux.yml (PyCharm Linux)
- runUiOctopusTests.yml (Octopus macOS)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Updated all UI test workflow prompts to instruct Claude Code to
automatically create fixes when concrete solutions are identified:
1. Create a branch with descriptive name
2. Apply the suggested fix to the codebase
3. Run the specific failing test to verify the fix works
4. Create a PR if the test passes with clear documentation
Each workflow includes the appropriate test command for its IDE type:
- IntelliJ/Octopus: gradle :tests:ui-ij-tests:testUi --tests "..."
- Rider: gradle :tests:ui-rd-tests:testUi --tests "..."
- PyCharm: gradle :tests:ui-py-tests:testUi --tests "..."
This enables fully automated test fix proposals without manual
intervention, reducing the feedback loop for fixing flaky or broken
UI tests caused by platform changes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Clarified that existing UI tests without OS specification run on macOS
by updating workflow names to include "macOS" suffix.
Created Linux versions of Rider and PyCharm UI tests:
- runUiRdTestsLinux.yml: Rider tests on Linux with Xvfb setup
- runUiPyTestsLinux.yml: PyCharm tests on Linux with Xvfb and Python 3.10
Both new workflows follow the same Linux setup pattern as the existing
runUiTestsLinux.yml workflow, using x11grab for screen recording and
appropriate IDE type parameters (-PideaType=RD/PC).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
