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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment