nunit-core team mailing list archive

[Simone Busoli <1057981@xxxxxxxxxxxxxxxxxx>]

Hello, I've pushed the changes to a new branch, please have a look at
the description of the merge request for details.

Charlie, I didn't take any decision with regards to how to handle
solution projects built for fx > 2.0 so in order to run the build you
need to have 4.5 and specify net-4.0 as the target via nant (apparently
it still doesn't explicitly support .NET 4.5). I guess it would make
sense to put some conditionals in the build scripts, but it's a bit
confusing, specifically because this feature is available also for the
net-2.0 build so it would make sense to run its tests even in that case,
but then I'm not sure how you could build the test assembly if you have
specified the net-2.0/3.5 targets, as the build will fail. Maybe an
override specifically for that project? I kept the changes in that
regard to the minimum so you have have a look at how it would make sense
to handle it.

** Branch unlinked: lp:~simone.busoli/nunitv2/async-support

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

Title:
  C#5 async tests are not supported

Status in NUnit Test Framework:
  Triaged
Status in NUnitLite Testing Framework:
  Triaged
Status in NUnit V2 Test Framework:
  In Progress

Bug description:
  If a method is marked async, nunit does not recognise it as a test,
  and some test runners may incorrectly  pass it while it is still
  running. These methods actually return a Task not void, and the test
  can only be passed if the task completes without a failure.

  As detailed here http://anthonysteele.co.uk/async-and-await-with-nunit

  MSTest supports async tests
  http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/13/what-s-new-for-mstest-unit-tests-in-visual-studio-11-beta.aspx

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions