Search Issue Tracker
In Progress
Fix In Review for 1.4.5
Votes
2
Found in [Package]
1.4.4
Issue ID
DSTR-1045
Regression
Yes
ITestRunCallback.RunStarted and ICallbacks.RunStarted are not called when running Test Runner tests in "PlayMode"
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the Test Runner window (Window > General > Test Runner)
3. Select the "PlayMode" tab
4. Press the “Run All” button
5. Observe the Console window
Expected result: “RunStarted” is called
Actual result: “RunStarted” is not called
Reproducible with: 1.4.4 (2021.3.38f1, 2022.3.28f1, 6000.0.1f1)
Not reproducible with: 1.4.3, 2.0.1-pre.18 (2021.3.38f1, 2022.3.28f1)
Couldn't test with: 2.0.1-exp.1, 2.0.1-pre.18 (6000.0.1f1) (Test Framework throws a compilation error)
Fixed in: 2.0.1-exp.1 (2021.3.38f1, 2022.3.28f1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- “Property offset falls outside of range for type in GetPropertyData” errors are thrown when using MaterialPropertyBlock.CopySHCoefficientArraysFrom
- Texture 2D reference links to missing documentation
- [Search] Help (?) does not work as a Search Filter
- Quest apps lose head and controller tracking
- Double separation lines are present in a kebab dropdown menu
Resolution Note (fix version 1.4.5):
Fixed an issue where RunStarted event was not being evoked correctly during a test run.