Bug 4035 - NUnit addin could auto-insert a breakpoint when running a single test
Summary: NUnit addin could auto-insert a breakpoint when running a single test
Status: RESOLVED DUPLICATE of bug 813
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: NUnit ()
Version: Trunk
Hardware: PC Mac OS
: Low enhancement
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on: 813
Blocks:
  Show dependency tree
 
Reported: 2012-03-22 13:56 UTC by Alan McGovern
Modified: 2013-02-14 03:57 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 813

Description Alan McGovern 2012-03-22 13:56:49 UTC
When I run a single nunit test with the debugger attached, the addin could automatically insert a breakpoint in the first line of the test body. Typically I run a single test in this manner to diagnose why it's failing and this would remove the need to manually add a breakpoint to it before choosing to run with debugger.
Comment 1 Mikayla Hutchinson [MSFT] 2012-03-22 14:06:23 UTC
This sounds like it would use the "run to location" debugger feature requested in bug 813.
Comment 2 Mike Krüger 2013-02-14 03:57:40 UTC
I think 813 is the better approach.

*** This bug has been marked as a duplicate of bug 813 ***