nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Public bug reported:

Per Ian Bavey:

We looked at the bug that has been logged by some customers where NUnit
tests can’t be debugged using the Unit Test Explorer and we tracked it
down to a problem in NUnitTestExecutor.cs. If line 67 in
NUnitTestExecutor.cs is changed

FROM:
   var selectedTestsMap = assemblyGroup.ToDictionary(tc => tc.DisplayName);

TO:
   var selectedTestsMap = assemblyGroup.ToDictionary(tc => tc.FullyQualifiedName);

then debugging works. Is that something you can update and publish soon?
I think it would make a lot of users happy.

See discussion on VS Code Gallery

** Affects: nunitv2
     Importance: High
     Assignee: Charlie Poole (charlie.poole)
         Status: Triaged


** Tags: vs-adapter

** Changed in: nunitv2
       Status: New => Triaged

** Changed in: nunitv2
   Importance: Undecided => High

** Changed in: nunitv2
     Assignee: (unassigned) => Charlie Poole (charlie.poole)

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/992837

Title:
  Unable to Debug using VS Test Adapter

Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  Per Ian Bavey:

  We looked at the bug that has been logged by some customers where
  NUnit tests can’t be debugged using the Unit Test Explorer and we
  tracked it down to a problem in NUnitTestExecutor.cs. If line 67 in
  NUnitTestExecutor.cs is changed

  FROM:
     var selectedTestsMap = assemblyGroup.ToDictionary(tc => tc.DisplayName);

  TO:
     var selectedTestsMap = assemblyGroup.ToDictionary(tc => tc.FullyQualifiedName);

  then debugging works. Is that something you can update and publish
  soon? I think it would make a lot of users happy.

  See discussion on VS Code Gallery

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/992837/+subscriptions