Search Issue Tracker

Fixed in 2018.4

Votes

0

Found in

2018.4.3f1

Issue ID

1169256

Regression

Yes

Using Assert.Inconclusive in editmode stops the running test

Unity Test Runner

-

1. What happened

Using Assert.Inconclusive in the tests in editmode stops the running test.
An exception is triggered and the running test stop.

ArgumentException: Requested value ‘Inconclusive’ was not found.

IndexOutOfRangeException: There are no more elements to process and IsTestComplete is false.

2. How we can reproduce it using the example you attached

2.1. Create the folder (Editor Tests) for edit mode (Window->General-> Test Runner).

2.2. Create a script (EditorTest.cs) on the folder that you created on the last step.

using NUnit.Framework;

public class EditorTest
{
[Test]
public void Test0()
{
Assert.True(true);
}

[Test]
public void Test1()
{
Assert.Inconclusive("Inconclusive test");

Assert.True(true);
}

[Test]
public void Test2()
{
Assert.True(true);
}
}

2.3. Run the Edit Mode tests (Window->General-> Test Runner->Run All).

Expected: all the test are executed.
Actual: An exception is triggered and the running test stop.

ArgumentException: Requested value ‘Inconclusive’ was not found.
IndexOutOfRangeException: There are no more elements to process and IsTestComplete is false.

This happens in Unity Unity 2018.4.3, but not in 2019.1.8 or 2018.3.6

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.