Summary:

Tests running in an Android Studio project with the Ladybug Feature Drop (build #AI-242.21829.142.2422.12345034) fail to initialize classes located outside of the "test" source set. This results in a java.lang.NoClassDefFoundError when attempting to use these classes within tests.

Expected Behavior:

Tests should be able to initialize and use classes from any source set within the project, including the "main" source set.

Actual Behavior:

Empty tests or tests initializing classes from the "test" source set run successfully.
Tests attempting to initialize classes from outside the "test" source set (e.g., "main") fail with a java.lang.NoClassDefFoundError.

Steps to Reproduce:

Create a new Android Studio project.
Define a class in the "main" source set (e.g., com.example. MyClass).
Write a test class in the "test" source set that attempts to initialize the class from step 2 (e.g., MyClass testObject = new MyClass();).
Run the test.

Observed Result:

The test fails with a java.lang.NoClassDefFoundError for com.example.MyClass.

Additional Information:

This issue occurs in both Ladybug Canary and Nightly builds.
The project is using JDK 21.

System Information:

Android Studio Version: Ladybug Feature Drop | 2024.2.2 Nightly 2024-09-10 (Build #AI-242.21829.142.2422.12345034)
Runtime Version: 21.0.3+-79915917-b509.11 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
OS: macOS 14.6.1

Non-Bundled Plugins:

com.databricks (1.3)
Statistic (4.3.1)
Batch Scripts Support (1.0.13)
org.jetbrains.compose.desktop.ide (1.6.2)
mobi.hsz.idea.gitignore (4.5.3)

Severity:

This bug can be considered a blocker for development as it prevents tests from interacting with core project functionality.