NUnit Framework

VisualState.xml should be saved *before* running tests

Bug #1111633 reported by mod852021
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Triaged
Low
Unassigned

Bug Description

VisualState.xml should be saved right before executing tests, because now if NUnit.exe dies during test execution, the last settings (categories/checkboxes) are lost.

I debug my NUnit project from Visual Studio by using NUnit.exe as the "start external program" - which is very convenient, because I just hit F5 to launch NUnit UI with my tests loaded automatically. However, when I stop debugging (Shift-F5), Visual Studio kills NUnit.exe, and the settings are frequently lost. This has been a pain-point.

Please fix this.

Tags: gui github
mod852021 (mod-launchpad-2013-01-31)
information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Charlie Poole (charlie.poole) wrote :

Interesting point. I'll investigate whether we can catch the shift-F5 shutdown and save first. If not, your idea seems reasonable.

Charlie

Changed in nunitv2:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
mod852021 (mod-launchpad-2013-01-31) wrote :

Thanks, Charlie, for looking into it.

BTW, I forgot to thank you for the awesome tool+framework NUnit is!

Charlie Poole (charlie.poole)
affects: nunitv2 → nunit-3.0
Revision history for this message
Charlie Poole (charlie.poole) wrote :

Moved issue to https://github.com/nunit/nunit-gui/issues/10

Changed in nunit-3.0:
status: Triaged → Won't Fix
Charlie Poole (charlie.poole)
Changed in nunit-3.0:
status: Won't Fix → Triaged
tags: added: github
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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