Test Iteration 2024.44

[github-actions[bot]]

Test Plan

1. Set up local test environment

• [ ] Assing this ticket to yourself and move it to the In Progress column.
• [ ] 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
• [ ] Clone this repository
• [ ] Download jq
• [ ] Run the upgrade_gradle.sh file to update all the wrappers
• [ ] Run git clean -fdx to remove build artifacts from all sample projects
• [ ] Make sure Android Home is configured in IDEA (Android Plugin required)
  • 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) https://www.jetbrains.com/help/idea/gradle-jvm-selection.html#jvm_settings

2. Document components

• [ ] Operating System:
  • Click the Apple icon, About This Mac
• [ ] Gradle version:
  • run gradle --version
• [ ] 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 Stable version (with build number):

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

3.1 Global issues

The following problems persists across all scenarios (most often IDE or Gradle-plugin related issues). If any of the following scenarios are fixed, delete the line in generateTestPlan.groovy

• [ ] IDEA-353787 - When projects are imported, they report a CopyProcessingSpec deprecation warning.

Scenarios in build-src

• [ ] Can navigate to plugin implementation from generated plugin accessors
• [ ] Class from buildSrc is available in the build script
• [ ] Project import finishes without warning
• [ ] Code completion available for settings script in project root directory
• [ ] Kotlin plugin implemented in buildSrc can use another class
• [ ] Java plugin implemented in buildSrc can use another class
• [ ] Groovy plugin implemented in buildSrc can use another class
• [ ] Code completion available in build-src/settings.gradle.kts

Scenarios in included-build-src

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

Scenarios in multiproject

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

Scenarios in java-build-src

• [ ] Project import finishes without warning
• [ ] 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

• [ ] Project import finishes without warning

Scenarios in error-in-build-script

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

Scenarios in test-launcher

• [ ] Running test with TestLauncher API

Scenarios in property-assignment

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

4. Finalize

• [ ] If you encountered a scenario that has been fixed, then remove the Known issue reference from the sources.
• [ ] Commit and push all changes (including the wrapper update)
• [ ] Tag the issue with the new-regresssion-reported label if you reported something to JetBrains
• [ ] Close this issue
• [ ] 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

[corrosive4354]

Set up the local environment

You can try using servbay, which currently supports one-click deployment of mongoDB/php/nodejs/mariadb