nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Generally, odd things are known to happen when  both
  Reload before each test run
  Reload when test assembly changes
are set.

I can't think of any reason to use both of them, since it
will cause an extra reload. However, they are separately
selectable - possibly an error in the design.

Can you try turning off both of them and then try each
separately? You can simulate an automatic reload by
using reload tests.

Note that the menu option reload project is a complete
reload, while reload tests tries to keep around old info
about tests that passed and failed. Reload fixture is
also a complete reload, but limits the load to only one
branch of the tree.

Charlie


On Mon, Sep 5, 2011 at 10:18 AM, David Mason <841894@xxxxxxxxxxxxxxxxxx> wrote:
> All of the following are enabled:
>
> Assembly Isolation:
>  Test run in NUnit process
>  Use seperate AppDomain per Assembly
>
> Assembly Reload:
>  Reload before each test run
>  Release when test assembly changes
>
> If I right click the assembly and "load fixture", it lets me run the
> test once more, and then disables it.
>
> --
> You received this bug notification because you are the registrant for
> NUnit V2.
> https://bugs.launchpad.net/bugs/841894
>
> Title:
>  UI won't run tests marked Explicit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/841894/+subscriptions
>

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/841894

Title:
  UI won't run tests marked Explicit

Status in NUnit V2 Test Framework:
  New

Bug description:
  NUnit 2.5.10, Gui runner:

  A test marked [Explicit] can only be run from the Gui runner if it is
  the first test run. After that, it is disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/841894/+subscriptions