Re: Error with automatic rerun of tests, 2.4.4

Hi Brad,

Here's a quick theory, which - if you verify it - might
save a lot of discussion.

I'm guessing that at some point in your experimentation,
you look at the assembly options General page and then
click OK. There's a bug in that page, fixed in source,
which causes only one of the buttons to be on at any
one time - in other words, all the radio buttons on
the form are treated as a single group. This happened
when I "re-styled" the page removing the group boxes
that used to be there.

I'm not sure, but it's also possible that this could
happen if you display /any/ settings page and then
click OK. I saw that behavior in at least one state
of the code.

If that's the case, we need go no further. Otherwise,
lets look more closely.

Charlie

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf 
> Of Brad Stiles
> Sent: Wednesday, November 14, 2007 12:11 PM
> To: [email protected]
> Subject: [Nunit-users] Error with automatic rerun of tests, 2.4.4
> 
> Charlie,
> 
> I haven't posted on this before now because I haven't been 
> able to consistently reproduce it, i.e. can't provide an exact recipe.
> 
> The folling Options=>Test Loader=>Assembly Reload options 
> have been set from a previous run, and I've verified that 
> they stick: "Reload before each test run", "Reload when test 
> assembly changes" and "Rerun last tests run".
> 
> I load Visual Studio with my project, build once to ensure 
> all assemblies are where they should be, then start up 
> nunit.exe with the assembly to be tested provided on the 
> command line.  I execute all the tests once, then switch over to VS.
> 
> I then engage in coding, periodically building to run the 
> tests.  For a while, the tests will re-run automatically.  I 
> can tell, because I sometimes change over to the NUnit gui to 
> check a Console.Out or something, and can see that the test I 
> added or broke from the last time is present and running.
> 
> However, at some point which may potentially pertain to time, 
> or number of builds, or something else I haven't been able to 
> determine, the re-runs stop.  I first noticed this behavior 
> because I'd just coded a test and built, so expected it to 
> fail.  When the task bar icon didn't flash at me, I switched 
> over to see what was up.
> 
> I've see two results.  One is where the build succeeded 
> (double checked it), but the NUnit gui shows the *previous* 
> set of tests, all with green bars, as if the assembly hadn't 
> been rebuilt or reloaded.  The other result is where NUnit 
> apparently *loaded* the new tests, I can see the new one, but 
> didn't run them, i.e. there's no test results.
> 
> I'm going to try different combinations of the Assembly 
> Reload options to see if I can pin anything down.  I'm just 
> letting you know in case anything jumps out at you before I 
> can figure something out.
> 
> Thanks,
> Brad 
> 
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and 
> a browser.
> Download your FREE copy of Splunk now >> 
> http://get.splunk.com/ _______________________________________________
> Nunit-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-users
> 



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/