No source information found for async test methods

Bug #1076012 reported by Charlie Poole
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Test Adapter
Fix Released
High
Charlie Poole

Bug Description

Async test methods all show no source information found. This is due to a problem in Diasession, which returns a null for the filename and int.MaxValue for the line number.

Related branches

Changed in nunit-vs-adapter:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 0.94
Revision history for this message
Charlie Poole (charlie.poole) wrote :

It's possible to create a workaround for this if one has the MethodInfo for the test available. However, the way we are using NUnit, we don't have actual access to the Test containing a MethodInfo, but only get a TestNode, which is a logical representation of a test, divorced from its implementation.

We would need to create a special runner as part of the test adapter rather than using the standard interfaces to NUnit. Some of the code from nunit.core would need to be repurposed for this.

Right now, it's being postponed from 0.94.

Changed in nunit-vs-adapter:
milestone: 0.94 → none
Revision history for this message
Charlie Poole (charlie.poole) wrote :

I decided to keep NUnit unchanged and put all the code for accessing the methodinfo and figuring out if it's for an async method in the adapter. That keeps NUnit cleaner.

Changed in nunit-vs-adapter:
milestone: none → 0.94
status: Triaged → Fix Committed
Changed in nunit-vs-adapter:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.