Search Issue Tracker
By Design
Votes
0
Found in
5.6.1f1
Issue ID
935265
Regression
No
LogAssert.Expect(LogType.Error, message) fails if frames were skipped
How to reproduce:
1. Open the "AssertError" project
2. Open the Test Runner
3. Run tests, "Test" fails
Expected result: "Test" test should pass.
Reproducible with: 2017.3.0a2, 2017.2.0b5, 2017.1.0p1, 5.6.3f1, 5.6.1f1.
Note: "Test2" is the same script as "Test" just without frame skipping (It passes).
________________________
This is by design. One can only LogAssert on a message that has been just logged if you do it in the same frame. If you skip frames, you have to LogAssert before the actual call generating the log. So, the test rewritten like this works:
[UnityTest]
public IEnumerator TestDebugLog()
{
LogAssert.Expect(LogType.Error, "Testerror");
yield return null; yield return null;
Debug.LogError("Testerror");
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment