nunit-core team mailing list archive

[Simone Busoli <1071714@xxxxxxxxxxxxxxxxxx>]

The fix will supports these scenarios, with actors core and fx and in
flavors old (<= 2.6.1), 2.6.2, and new (> 2.6.2):

1. old core - fx 2.6.2 is NOK, as above
2. old core - new fx is OK: core puts the data in the illogical context and fx is able to retrieve it from there. Of course the feature of having the ContextDictionary flow across threads is not there but this is obvious
3. core 2.6.2 - old fx is OK, as above
4. core 2.6.2 - new fx is OK: core puts data in the logical context, fx will pick it up from there
5. new core - old fx is OK: core puts data in the logical context, fx will pick it up from there
6. new core - fx 2.6.2 is OK: core puts data in the logical context, fx will pick it up from there

** Changed in: nunitv2
       Status: In Progress => Fix Committed

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

Title:
  TestContext is broken when a previous version of the runner is used
  alongside a new version of the framework

Status in NUnit V2 Test Framework:
  Fix Committed

Bug description:
  With 2.6.2 support for flowing TestContext across threads, mainly for supporting async tests was introduced.
  The way it was implemented broke the scenario (regardless of whether async tests or not) in which a previous runner along with the 2.6.2 framework was used.

  We should support backwards and forward compatibility if possible.

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