Run a single test in IntelliJ about testparameterinjector HOT 12 CLOSED

Hi, my team and I are really interested on using this library!
Would be great to have the ability to run tests individually.
Please let me know if we can help

from testparameterinjector.

Correct me if I'm wrong, but Android Studio is backed by IntelliJ, right?

If so, this is a feature request that is on our radar. After some initial analysis, we believe the best fix for this is to update the IntelliJ JUnit4TestRunnerUtil.java.

from testparameterinjector.

@alexjski was working on this last time we spoke

from testparameterinjector.

According to IntelliJ, this should be fixed in their next release (2021.3)

from testparameterinjector.

https://youtrack.jetbrains.com/issue/IDEA-275586 is fixed in 213.2441 build. I also validated the version at head does not suffer from the problem anymore.

Thank you, @akozlova for fixing that!

from testparameterinjector.

Hi,

What tool are you using to run the single test?

from testparameterinjector.

I run it with the Android Studio option on each test for a kotlin app.

from testparameterinjector.

I sent a PR for Intellij which addresses the issue. The problem with that if it is merged, my understanding is that it will be made available in next intellij release, so until then (and users picking up the new version) the problem remains.

We could also apply a workaround on our side, however it is not possible to have parameter values filtered correctly with that. In fact, I believe such workaround would make it at least more complicated to reconcile with a proper fix on the IDE side. My preference would be to try to get the fix in for Intellij and just encourage users to update -- please let me know if that is not an acceptable solution.

from testparameterinjector.

Hi @alexjski, if by is not possible to have parameter values filtered correctly you mean the individual test will run as many times as parameter values has, that would be totally ok for me 👍 Waiting for JetBrains + Android Studio to integrate the fix is gonna take a while.. Anyway, thanks for your help! Appreciate it

from testparameterinjector.

I use a temporary workaround for that:
as soon as someone wants to run a test method individually from AndroidStudio (IntelliJ IDEA) just comment out the line with @RunWith(TestParameterInjector::class) and use only test class properties (not test method parameters) with annotation @TestParameter and a default value for it.
;-)
You can put a comment about that restriction/workaround above the test class to help your colleagues with the approach.

from testparameterinjector.

Hi @alexjski, if by is not possible to have parameter values filtered correctly you mean the individual test will run as many times as parameter values has, that would be totally ok for me Waiting for JetBrains + Android Studio to integrate the fix is gonna take a while.. Anyway, thanks for your help! Appreciate it

The problem we are facing is that the test runner in Intellij creates an opaque Filter which does not include the information about the parameter value, hence without the information, the best we can do is to run all combinations. I agree this is not the end of the world, but I wanted to test the ground about just getting that done in Intellij rather than adding a workaround internally and later deal with removing it.

The workaround is obvious -- run all combinations (in fact, I have a change lying around doing that exactly). The problem with it is that once Intellij does the right thing, then the workaround may hurt the usability and should eventually be removed (when?). This is why not creating a workaround internally is so tempting -- I hope that makes sense to you. I don't know if and when the PR for Intellij will be submitted and released -- if that was to happen soon, I would actually opt to say "please update your IDE". If it is the opposite/a lot of users must use older Intellij for a foreseeable future, that definitely changes the equation.

I think what I am hearing is that I should try a little harder (I may need to sacrifice some edge cases) to get the fix out quicker.

from testparameterinjector.

According to IntelliJ, this should be fixed in their next release (2021.3)

I tested that at head and the problem still prevails. Filed https://youtrack.jetbrains.com/issue/IDEA-275586 for it.

from testparameterinjector.