Test Iteration 2023.50

[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 Android Home is configured in IDEA
  • Go Preferences > Build, Execution, Deployment > Android > Android Project Structure > SDK Location
• [ ] Make sure that for scenario 03-multiproject JDK 17 is used (Spring Boot plugin requirement)

2. Document components

• [x] Operating System:

  • Click the Apple icon, About This Mac 14.2.1 (23C71)

• [x] Gradle version:

  • run gradle --version

    Gradle 8.7-20240102001240+0000

  Build time: 2024-01-02 00:12:40 UTC Revision: 1501cc643d9723e053739128ac718145210e3185

  Kotlin: 1.9.20 Groovy: 3.0.17 Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023 JVM: 11.0.21 (Amazon.com Inc. 11.0.21+9-LTS) OS: Mac OS X 14.2.1 aarch64

• [x] IntelliJ Idea EAP version (with build number):

  • Open JetBrains Toolbox, click the Settings gear icon next to an install, go to the About tab IntelliJ IDEA 2023.3.2 (Community Edition) Build #IC-233.13135.103, built on December 20, 2023 Runtime version: 17.0.9+7-b1087.9 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 14.2.1 GC: G1 Young Generation, G1 Old Generation Memory: 2048M Cores: 10 Metal Rendering is ON Registry: debugger.new.tool.window.layout=true ide.experimental.ui=true Non-Bundled Plugins: com.github.copilot (1.4.5.4049) org.jetbrains.android (233.13135.106) Kotlin: 233.13135.103-IJ

• [x] IntelliJ Idea Stable version (with build number): same as above (it seems no EAP was available at that time

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

Scenarios in included-build-src

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

Scenarios in multiproject

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

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

Scenarios in property-assignment

• [x] Kotlin single value property assignment should be supported
• [x] Kotlin filesystem location property assignment should be supported
• [x] Kotlin set property assignment should be supported
• [x] Kotlin map property assignment should be supported

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

[reinsch82]

Done