Fully qualified name not used in re-run, tests executed across multiple unit test projects in the same solution about dotnet-test-rerun HOT 9 CLOSED

Hi @jwias,

We will take a look into this in the next days.
Thanks for the feedback and for helping to continue improving this tool.

We'll come back to you as soon as we can.

from dotnet-test-rerun.

Hi @jwias,

Initially the tests that require the test browser are not run? Is the retry that triggers them because they have the same name?

If that's so would it solve the issue if the rerun filter was something like this: (TestCategory=API & TestCategory=SmokeTests)&(FullyQualifiedName~Test1) ?

from dotnet-test-rerun.

Hi @ricardofslp

The issue appears when there's the same test name yes, in the particular example I mentioned - I have API tests only that do not initialise a web browser for UI tests, so when the rerun kicks in, it can also trigger tests that are in this UI test project, if the test names do match (I have instances of this)

Retaining filters I think would solve part of the issue for sure, in theory it could still match though with duplicate tests that fall under the same category? Is it not possible to have the actual fully qualified test name? or at least include the testing class as well as the test method(name), to try and ensure something more unique other that just test method(name)?

I of course simplified my original example, but there's also situations where I have duplicate test names within the same test project/test category, so I have things like

MyTests.API.CRUD.Test1
MyTests.API.Scenarios.Test1
etc.

Both of these tests could still be triggered by your example filter, because they both match the expression.

Having the re-run, only run the exact test that failed, would be excellent.

from dotnet-test-rerun.

Hi @jwias,

Could you please try this alpha version https://www.nuget.org/packages/dotnet-test-rerun/1.5.1-alpha.0 we've released to see if at least avoids the need to add the browser to the test api test stack?

Regarding only triggering the actual test we're still investigating the best way of doing that. Will need to test one option that I see as possible.

from dotnet-test-rerun.

Hi @ricardofslp this works great solving the first scenario! Very much looking forward to the second scenario being resolved.

Thank you for jumping on this so quickly, very much appreciated :)

from dotnet-test-rerun.

Hi @jwias,

Can you please test this alpha version https://www.nuget.org/packages/dotnet-test-rerun/1.6.0-alpha.0 ?
I think it can work for the second scenario.

from dotnet-test-rerun.

@ricardofslp this looks absolutely perfect! I've tested this, and it seems to solve the second scenario perfectly

from dotnet-test-rerun.

Hi @jwias ,

That is great we will release this in an official version soon.

from dotnet-test-rerun.

Official version has been released.
Please close this issue if the test succeeds

from dotnet-test-rerun.