You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi! IIRC these Ids are created by the VSTest common test class objects, and not by any NUnit specific part at all.
That said, I am not sure why it is varying, my understanding is that the TestId in the trx file represents the test itself, and is a hash of the path and fully qualified name of the test method. That should be a stable guid.
And, when I test it locally (inside VS), I don't find any changes from run to run. On a build server however, this would change, since the path might change from build to build.
When I test it on the command line however, I get the exact same results that you do, they indeed do vary. No clue why though. I'll ping this to some MS guy and ask if they know.
But in any case, this is not adapter related.
@GraueEminenz79@OsirisTerje
We recently made trx generate hierarchical results for adapters which send hierarchical results.
For supporting both non-hierarchical and hierarchical results, we made some code changes which caused test guid id to change.
We have fixed this issue. Vstest issue link: microsoft/vstest#1783
Given is one Unit Test named
MyTest
in assemblySomeAssemblyWithOneUTest.dll
.With every execution
different
testId
s for the test are generated.Is this intended by design?
1st execution (trx content condensed)
hence testId="f5932e8a-b639-445f-85ee-28b735f1d512"
2nd execution (trx content condensed)
hence testId="63d6697b-c276-471e-89a1-b2e4a963256c"
EDIT:
To rule out that the
adapterTypeName
has changed in between, under<TestDefintions>
the entries are identical:The text was updated successfully, but these errors were encountered: