Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Async tests which use Assert.Inconclusive report as Error

See original GitHub issue

Description

Steps to reproduce

   [TestMethod]
        public void TestInconclusiveSync()
        {

            Assert.Inconclusive("This will report as skipped");
        }

        [TestMethod]
        public async Task TestInconclusiveAsync()
        {

            Assert.Inconclusive("This will report as error");
        }

v1.1.18

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:16 (13 by maintainers)

Top GitHub Comments

2reactions

AbhitejJohncommented, Oct 1, 2017

@jthelin : Sorry about that. The builds are failing because of service issues. Should be up this week hopefully.

1reaction

jthelincommented, Oct 16, 2017

Confirming this issue is fixed for me now that v1.2.0 nuget packages published.

Top Results From Across the Web

c# - Calling Assert.Inconclusive() in an async unit test is ...

When the test is exercising some async methods, and the [TestMethod] signature returns Task then the test is reported in the TestExplorer as...

Calling Assert.Inconclusive() in an async unit test is reported ...

Coding example for the question Calling Assert.Inconclusive() in an async unit test is reported as a fail-C#. ... use Assert.Inconclusive report as Error....

Calling Assert.Inconclusive() in an async unit test is ...

Your question system cancels everything without warning if you type ESC key, I'm not typing it all again. Visual Studiowindows 10.0visual studio ...

Assert.Inconclusive

The Assert.Inconclusive method indicates that the test could not be completed with the data available. It should be used in situations where another...

Unit Test Sessions reports "Inconclusive: Test not run"

I'm using NUnit, NSubstitude, netcore 2.2 and newest Rider 2019.2, ... Tests are either ignored or reports inconclusive error.