Test Iteration 2023.35

[github-actions[bot]]

Test Plan

1. Set up local test environment

• [x] Assing this ticket to yourself and move it to the In Progress column.
• [x] Install IntelliJ IDEA (if you don't already have it installed), both the EAP and latest stable releases
  • Tip: you can use the Toolbox App to manage multiple installations
• [x] Clone this repository
• [x] Download jq
• [x] Update Gradle wrappers in all sample projects to the latest snapshot
  • One-liner bash/zsh update command: for sample in $(ls | grep -e '^[0-9][0-9].*'); do cd $sample; ./gradlew wrapper --gradle-version nightly; cd -; done
• [x] Run git clean -fdx to remove build artifacts from all sample projects
• [x] Make sure the ANDROID_HOME environment variable is properly set on you machine
• [x] Make sure that for scenario 03-multiproject JDK 17 is used (Spring Boot plugin requirement)

2. Document components

• [x] Operating System:
  • Mac OS X 13.5.1 aarch64
• [x] Gradle version:
  • Gradle 8.5-20230904225832+0000
• [x] IntelliJ Idea EAP version (with build number):
  • IU-232.9559.62
• [x] IntelliJ Idea Stable version (with build number):
  • IU-232.9559.62, same as EAP

3. Verify scenarios

These scenarios are automatically generated from the lines starting with TODO (scenario) in the build script and code files.

The sample projects are located in the numbered folders in the repository root. For each project, follow the steps below:

• Launch IDEA EAP
• Import the sample project into IDEA and wait for the project sync to finish
• Use text search to locate the scenario (listed below) in the build and follow the instructions
• Check off the verified scenario in the list below

In case of a failure:

• Verify the same scenario in the latest released IDEA version
• Open an issue at https://youtrack.jetbrains.com
• Link the issue in the sample project:
  • Add the following comment to the failing line // Known issue: https://youtrack.jetbrains.com/issue/IDEA-123456
• add an X (red cross emoji) to the list below and link the created issue there as well

Scenarios in build-src

• [x] Can navigate to plugin implementation from generated plugin accessors
• [x] Class from buildSrc is available in the build script
• [x] Project import finishes without warning
• [x] Code completion available for settings script
• [x] Kotlin plugin implemented in buildSrc can use another class
• [x] Java plugin implemented in buildSrc can use another class
• [x] Groovy plugin implemented in buildSrc can use another class
• [x] Code completion available for settings script here

Scenarios in included-build-src

• [x] Project import finishes without warning
• [x] Kotlin plugin implemented in included build can use another class
• [x] Java plugin implemented in included build can use another class
• [x] Groovy plugin implemented in included build can use another class

Scenarios in multiproject

• [x] Runs application with Gradle task from included build
• [x] Extension from plugins applied in Groovy precompiled script plugin is available
• [x] Resources from test configuration are not available in the main source set
• [x] Running integration test picks the correct test task
• [x] Groovy precompiled script plugin can reference classes from the same source set Known Issue
• [x] Project import finishes without warning
• [x] Extension from plugin applied in Kotlin precompiled script plugin is available

Scenarios in java-build-src

• [x] Project import finishes without warning
• [x] Java plugin implemented in buildSrc can use another class if there isn't a top-level build.gradle.kts

Scenarios in version-catalog-build-src

• [x] Project import finishes without warning (Known Issue) https://github.com/melix/jmh-gradle-plugin/issues/235

Scenarios in error-in-build-script

• [x] validate broken script behavior when exception happens in script body
• [x] validate broken script behavior when exception happens in callback

Scenarios in test-launcher

• [x] Running test with TestLauncher API

4. Finalize

• [x] If you encountered a scenario that has been fixed, then remove the Known issue reference from the sources.
• [x] Commit and push all changes (including the wrapper update)
• [x] Tag the issue with the new-regresssion-reported label if you reported something to JetBrains
• [x] Close this issue
• [x] Consider improving the test plan
  • If you find that some scenarios are incorrect, redundant, missing, etc. please provide a PR and ask the @bt-ide-experience-team for a review
  • You can update the issue template here: https://github.com/gradle/ide-smoke-tests/blob/main/generateTestPlan.groovy

[hegyibalint]

Running integration test picks the correct test task.

@donat Should we check the gradle.testLauncherAPI.enabled status before?

[donat]

@donat Should we check the gradle.testLauncherAPI.enabled status before?

You are right. All smoke tests should be using gradle.testLauncherAPI.enabled.