apache / apache/grails-intellij-plugin

Inspections stop working after running Groovy tests

Open
#383 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

Since the last update (2022.3.1) on my IntelliJ Ultimate Edition, I've been having issue with the inspection. i'm developing in Grails. The inspection works whenever I start intelliJ but at some point it stops showing me warnings about 90% of my problems. For example it still shows unused variables, but does not show unknown variable (if I mistype the name for example).

I've been researching, reinstalling IntelliJ entirely, reinstalling the Grails plugin (that allows the inspection) but nothing works.

---

Project sample in the attachments

STR:

- Open the project in IDEA

- Go to `src/integration-test/groovy/Test`

- Observe that inspection is properly working:
_⚠️ attachment `image.png` was not included in the export_

- Run "test save" method

- Check the inspection once again:
_⚠️ attachment `image1.png` was not included in the export_

- IDE restart helps to restore inspection functionality. Switching tests runner from Gradle to IntelliJ IDEA also helps to workaround the problem

Works fine in 2022.2.4

---

*2 attachment(s) referenced here (`image.png`, `image1.png`) are not part of the CSV export.*
*Imported from [IDEA-313660](https://youtrack.jetbrains.com/issue/IDEA-313660) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the STR in src/integration-test/groovy/Test: open the project in IntelliJ IDEA, confirm inspections, run the "test save" method, and check whether unknown-variable warnings disappear. Compare the Gradle test runner with the IntelliJ IDEA runner, and verify that inspections still report unknown variables after the test runs without requiring an IDE restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.