← Back to team overview

nunit-core team mailing list archive

[Bug 1071714] [NEW] TestContext is broken when a previous version of the runner is used alongside a new version of the framework

 

Public bug reported:

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.

** Affects: nunitv2
     Importance: Undecided
     Assignee: Simone Busoli (simone.busoli)
         Status: In Progress

** Changed in: nunitv2
       Status: New => In Progress

** Changed in: nunitv2
     Assignee: (unassigned) => Simone Busoli (simone.busoli)

** Description changed:

  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 wether async tests or not) in which a previous runner along with the 2.6.2 framework was used.
+ 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.

-- 
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:
  In Progress

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


Follow ups

References