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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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
}