NUnit 3 console runs test for nunit.framework.dll v2 in parallel mode

[NikolayPianikov]

Is it expected behavior? If it is true the TC extensions works incorrectly for this case.
As I know nunit.framework.dll v2 have no attributes for parallel mode. And this issue is critical for the TC extension. Related issue is nunit/teamcity-event-listener#14

[rprouse]

I believe that NUnit 3 will run multiple NUnit 2 test assemblies in parallel, but the tests within the v2 tests will not be run in parallel. Is the trouble with multiple assemblies?

[NikolayPianikov]

Yes, the the trouble with multiple assemblies.

[rprouse]

Why is this a problem for the TC extension? v3 tests run the same way. I assume you handle that?

[NikolayPianikov]

Extension receives 2 message one after another:

1:

<start-suite id="1-1005" name="C:\Projects\GitHub\nunit-teamcity-event-listener\bin\Debug\1167775801\mocks\MAP.Common.Test.dll" fullname="C:\Projects\GitHub\nunit-teamcity-event-listener\bin\Debug\1167775801\mocks\MAP.Common.Test.dll" />

2:

<start-suite id="1-1431" name="C:\Projects\GitHub\nunit-teamcity-event-listener\bin\Debug\1167775801\mocks\MAP.Web.Test.dll" fullname="C:\Projects\GitHub\nunit-teamcity-event-listener\bin\Debug\1167775801\mocks\MAP.Web.Test.dll" />

After that

3:
<start-suite id="1-1006" name="MAP" fullname="MAP" />

Question: What assembly corresponds <start-suite id="1-1006" name="MAP" fullname="MAP" /> ?
We have a bunch of unstructured messages from different assemblies

[NikolayPianikov]

Some kind of XML but from several different files at the same time :)
I can ignore starting blocks but I should know an assembly for each test.
Almost all the data lose value because there is no way to define their relationship.

[CharliePoole]

The issue is that the v2 driver is using the same prefix for both assemblies. Both drivers should get their prefixes from a common source.

[ChrisMaddock]

Fixed in #564 I believe.