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
I noticed that when running V3 tests with the V3 console against an assembly, the output XML's first test-suite element (with type="Assembly") has a name attribute, which is only the assembly name (like Foo.dll) and a fullname (like C:\Bar\Foo.dll).
Running V2 tests with the V3 runner and the nunit-v2-framework-driver seems to have C:\Bar\Foo.dll in both the name and fullname attribute.
I'd expect name to be the assembly file name with V2 tests as well.
Best regards,
Stefan Ilic
The text was updated successfully, but these errors were encountered:
I'm confirming this for both nunit 3 and nunit v2 tests run with output format nunit2. At the moment, it's unclear whether fixing the driver extension will fix both problems or if the nunitv2 output writer extension will require changes as well.
Hi,
I noticed that when running V3 tests with the V3 console against an assembly, the output XML's first test-suite element (with type="Assembly") has a
name
attribute, which is only the assembly name (likeFoo.dll
) and afullname
(likeC:\Bar\Foo.dll
).Running V2 tests with the V3 runner and the nunit-v2-framework-driver seems to have
C:\Bar\Foo.dll
in both thename
andfullname
attribute.I'd expect
name
to be the assembly file name with V2 tests as well.Best regards,
Stefan Ilic
The text was updated successfully, but these errors were encountered: