Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a1
2018.4.1f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1159355
Regression
Yes
[Test Runner] Start() and Update() methods are not called in Edit Mode tests
Steps to reproduce:
1. Download 1159355_repro project
2. Open Test Runner window
3. Run All test in Edit mode
Expected results: All test are a successful
Actual results: Start and Update method isn't called
Reproduced with: 2019.3.0a5, 2019.2.0b5, 2019.1.5f1, 2018.4.1f1
Not reproducible with: 2017.4.27f1
Note:
- Also reproducible in Play Mode tests
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Start and Update are called, but in inside tests, you need to skip a frame explicitly
To achieve this you need to convert a test into UnityTest, as shown below:
[UnityTest]
public IEnumerator MyTest()
{
yield return null; // skip the first frame
// do your assertions here
}