Search Issue Tracker

Fixed

Won't Fix in 2.0.X

Fixed in 1.4.2

Votes

0

Found in [Package]

1.1.31

1.4.0

2.0.1-pre.18

Issue ID

DSTR-469

Regression

No

[UnityTest] [Timeout] Failed test because of timeout returns assertion failure message instead of timeout message

Package: Test-Framework

-

How to reproduce:
1. Open the attached “TimeoutUnityTest.zip” project
2. In the Test Runner window expand “Test Run” > “Tests.dll” > “My Test”
3. Right-click on TestBug and press “Run”

Expected result: Test fails with message “Timeout value of 1234ms was exceeded”
Actual result: Test fails with message “Expected: 1 But was: 0”

Reproducible with: 1.1.31, 2.0.1-pre.18 (2019.4.36f1, 2020.3.31f1, 2021.2.16f1, 2022.1.0b11, 2022.2.0a9)

Notes:
- When test timeouts, the timeout message appears if the assertion would have returned true, otherwise the failed test message shows assertion results

Failed test message:
TestBug (1.256s)
---
Expected: 1
But was: 0
---
at MyTest+<TestBug>d__2.MoveNext () \[0x0003a] in /Users/mantas.kandrotas/Downloads/TimeoutUnityTest/Assets/Tests/MyTest.cs:21
at UnityEngine.TestTools.TestEnumerator+<Execute>d__7.MoveNext () \[0x0003a] in /Users/mantas.kandrotas/Downloads/TimeoutUnityTest/Library/PackageCache/com.unity.test-framework@1.1.31/UnityEngine.TestRunner/NUnitExtensions/Attributes/TestEnumerator.cs:46

  1. Resolution Note (fix version 1.4.2):

    A timeout message is now printed when the test failures occurs before the test finishes.

  2. Resolution Note (2.0.X):

    Won't do any 2.0 fixes, 2.0 is never going to be released

Log in to vote on this issue

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.

Latest issues

See all new issues