Fixed
Status Update
No update yet.
Comments
uc...@google.com
Not reproduced, can you share a sample project to reproduce this issue.
ma...@inova.si
Attaching. Run "Run all tests" to reproduce bug.
ma...@gmail.com
Attaching video of me reproducing the bug. For me it reproduces every time.
uc...@google.com
ja...@google.com
Leo, can you please figure out who should fix this?
le...@google.com
@Renaud, would you know more about this?
rp...@google.com
Lucas, didn't you fix this recently?
ls...@google.com
I fixed for packages. Apparently the whole project is not working yet. I'll have a look.
#1, Thank you for filing the bug
#1, Thank you for filing the bug
ls...@google.com
It's a non-deterministic failure probably related to IDE trying to find the test classes while in dumb mode because of build or indexing post build. (possibly related to
A simple workaround for now is to first run the test run configuration normally and then a second time removing the Gradle-aware before run task, which will avoid build right before running and avoid dumb mode conflict.
A simple workaround for now is to first run the test run configuration normally and then a second time removing the Gradle-aware before run task, which will avoid build right before running and avoid dumb mode conflict.
ls...@google.com
ad...@manichord.com
Thank you for the work around to removing the "Gradle-aware Make" task for the run config's "Before launch" setting for test run configs for single module and package-level.
That workaround consistently **fixes** the issue for me when running a module-level or package level config on Kotlin junit tests, whereas as soon as I edit the config adding back in "Gradle-aware Make" immediately causes the tests not to run with error message:
That workaround consistently **fixes** the issue for me when running a module-level or package level config on Kotlin junit tests, whereas as soon as I edit the config adding back in "Gradle-aware Make" immediately causes the tests not to run with error message:
Which is not quite the same error message I get when I try whole-project config where even with the "Gradle-aware Make" removed I get a slightly different error message:
>Process finished with exit code 1
>Class not found: "xxx.yyy.zzz.MyTest"Empty test suite.
>
Where "xxx.yyy.zzz.MyTest is the first (alphabetically sorted) Kotlin Test class that I have in my JUnit tests.
ls...@google.com
Status of this issue: Studio side fixed, waiting for Kotlin plugin for Intellij to fix the issue https://youtrack.jetbrains.com/issue/KT-24979
sa...@google.com
Thank you for the update Lucas.
al...@google.com
Assigning to Raluca to track Kotlin fix.
sa...@google.com
Rel team decision: Updated 3.2 branch with 1.2.60 prebuilts.
[Deleted User] <[Deleted User]>
This is not fixed on AS 3.2 Beta 5. I've just run the OP's reproduction steps again and I get "No tests were found".
In fact, I challenge somebody to show me just one single working solution for running all tests w/Kotlin support in Android Studio 3.2. They have been broken for the entire lifetime of this version, despite at least a dozen bug reports.
In fact, I challenge somebody to show me just one single working solution for running all tests w/Kotlin support in Android Studio 3.2. They have been broken for the entire lifetime of this version, despite at least a dozen bug reports.
Description
AI-173.4670197, JRE 1.8.0_152-release-1024-b02x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080, 1920x1080
Android Gradle Plugin: 3.1.0
Gradle: 4.4
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: pinned revision 3.1 not found; latest from SDK: (package not found);
CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: (not found);
Steps to reproduce:
1. Create new empty android project with Kotlin support
2. Create new JUnit configuration that runs all tests in package (leave package empty) in all projects - see attached image
3. Run this configuration
Tests will not run, complaining that ExampleUnitTest class is not found.