As you have mentioned, the statement Assert is used on whether the async
lambda throws a specific exception or not but since the lambda itself is
async-ed, do you mean to say that the assertion itself should be awaited ?
Jv
On Thu, Oct 25, 2012 at 12:51 PM, Simone Busoli
<email address hidden>wrote:
> Public bug reported:
>
> Although we support async test methods, we're not handling other async
> things properly. For instance this is not working as expected:
>
> Assert.That(async () => await DoSomething(), Throws.Exception);
>
> The reasons is the same as why we didn't support async methods: we are
> not waiting until the function has completed its execution.
>
> Additional details here: http://stackoverflow.com/questions/13056716
> /async-unit-tests-not-working-as-expected
>
> ** Affects: nunitv2
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
> https://bugs.launchpad.net/bugs/1071164
>
> Title:
> Support async methods in usage scenarios of Throws constraints
>
> Status in NUnit V2 Test Framework:
> New
>
> Bug description:
> Although we support async test methods, we're not handling other async
> things properly. For instance this is not working as expected:
>
> Assert.That(async () => await DoSomething(), Throws.Exception);
>
> The reasons is the same as why we didn't support async methods: we are
> not waiting until the function has completed its execution.
>
> Additional details here: http://stackoverflow.com/questions/13056716
> /async-unit-tests-not-working-as-expected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/1071164/+subscriptions
>
Hi Simone,
As you have mentioned, the statement Assert is used on whether the async
lambda throws a specific exception or not but since the lambda itself is
async-ed, do you mean to say that the assertion itself should be awaited ?
Jv
On Thu, Oct 25, 2012 at 12:51 PM, Simone Busoli
<email address hidden>wrote:
> Public bug reported: stackoverflow. com/questions/ 13056716 unit-tests- not-working- as-expected /bugs.launchpad .net/bugs/ 1071164 stackoverflow. com/questions/ 13056716 unit-tests- not-working- as-expected /bugs.launchpad .net/nunitv2/ +bug/1071164/ +subscriptions
>
> Although we support async test methods, we're not handling other async
> things properly. For instance this is not working as expected:
>
> Assert.That(async () => await DoSomething(), Throws.Exception);
>
> The reasons is the same as why we didn't support async methods: we are
> not waiting until the function has completed its execution.
>
> Additional details here: http://
> /async-
>
> ** Affects: nunitv2
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
> https:/
>
> Title:
> Support async methods in usage scenarios of Throws constraints
>
> Status in NUnit V2 Test Framework:
> New
>
> Bug description:
> Although we support async test methods, we're not handling other async
> things properly. For instance this is not working as expected:
>
> Assert.That(async () => await DoSomething(), Throws.Exception);
>
> The reasons is the same as why we didn't support async methods: we are
> not waiting until the function has completed its execution.
>
> Additional details here: http://
> /async-
>
> To manage notifications about this bug go to:
> https:/
>
--
Regards,
Ravichandran Jv ravichandranjv. blogspot. com
http://