Skip to content

docs: note Gradle test task caching in AGENTS.md - #892

Closed
rrama wants to merge 1 commit into
masterfrom
docs/agents-md-gradle-rerun-tasks
Closed

docs: note Gradle test task caching in AGENTS.md#892
rrama wants to merge 1 commit into
masterfrom
docs/agents-md-gradle-rerun-tasks

Conversation

@rrama

@rrama rrama commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Description

Adds a note to AGENTS.md's Development Workflow section: ./gradlew test can report UP-TO-DATE and exit 0 without running anything when the test task is cached, which looks identical to a genuine pass. Use ./gradlew test --rerun-tasks to confirm a real, non-cached green.

This consolidates guidance that was previously documented only on a shared cross-repo Confluence setup-instructions page. It's specific to this repo's own Gradle/IntelliJ build, so it belongs here instead.

Checklist

N/A: docs-only change (one line in AGENTS.md), no code/tests affected.

Screenshots / GIFs

N/A


Note

Low Risk
Documentation-only change to AGENTS.md; no code, build, or runtime behavior affected.

Overview
Adds one workflow bullet to AGENTS.md so agents and contributors know that ./gradlew test can finish with UP-TO-DATE and exit 0 when Gradle’s test task is cached—same as a real green run.

The new guidance says to use ./gradlew test --rerun-tasks when you need to force tests to run and confirm a non-cached pass. This moves repo-specific Gradle/IntelliJ advice from shared Confluence setup docs into the in-repo agent workflow section, next to the existing “run tests before commit” step.

Reviewed by Cursor Bugbot for commit cee9f82. Bugbot is set up for automated code reviews on this repo. Configure here.

Gradle can report UP-TO-DATE and exit 0 for a cached test task without
running anything, which looks identical to a genuine pass. This tip
was previously only on a shared cross-repo Confluence setup page, but
it's specific to this repo's own Gradle/IntelliJ build, so it belongs
in AGENTS.md instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@rrama
rrama requested a review from a team as a code owner September 2, 2026 18:30
@snyk-io

snyk-io Bot commented Sep 2, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@snyk-pr-review-bot

Copy link
Copy Markdown

PR Reviewer Guide 🔍

🧪 PR contains tests
🔒 No security concerns identified
⚡ No major issues detected
📚 Repository Context Analyzed

This review considered 5 relevant code sections from 5 files (average relevance: 0.84)

🤖 Repository instructions applied (from AGENTS.md)

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Code Coverage

Total Project Coverage 48.63%

@rrama

rrama commented Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

Superseded — this note already exists on #882 (the branch this belongs on), which I missed when opening this PR. Closing as redundant.

@rrama rrama closed this Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant