Bug 11017 - Run Test does not auto-save / build
Summary: Run Test does not auto-save / build
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: NUnit ()
Version: 4.0
Hardware: PC Linux
: Normal enhancement
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2013-03-09 07:13 UTC by Matt
Modified: 2016-11-03 10:34 UTC (History)
2 users (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 FIXED

Description Matt 2013-03-09 07:13:37 UTC
Description of Problem:

When selecting "Run Test" with the right click menu from the unit tests, files are not saved and built automatically.

Steps to reproduce the problem:
1. Open a Unit Test view. 
2. Edit a file (do not save).
3. Run a test (or debug the test).

Actual Results:

The edited file is not saved and the project is not rebuilt.


Expected Results:

The edited file would be saved and the project would be rebuilt prior to running the test.


How often does this happen? 

Always

Additional Information:
Comment 1 Marius Ungureanu 2016-11-03 10:34:09 UTC
This works in the current XS version (6.0+), hence closing this bug as fixed.