Search Issue Tracker
In Progress
Fix In Review for 1.4.4
Votes
0
Found in [Package]
1.3.7
Issue ID
DSTR-858
Regression
Yes
Test Runner hangs on building Player when the “Exercise 7: Solution” sample from Test Framework is run as a test
How to reproduce:
1. Create a new project using the “3D Core” template
2. Add the Test Framework Package
3. Add “Exercise 7: Solution” sample from Test Framework Package
4. If the “CS0006: could not be found” error is logged then restart the Editor
5. Open Test Runner (Window > General)
6. Select the “Play Mode” section
7. Select the “VerifyApplicationPlaying” test and run it (right-click > Run)
8. Observe the build progress and the Console
Expected result: The Player is built successfully, tests are run, and no warnings are logged to the Console
Actual result: The Player builds indefinitely, “No script asset”, and “The referenced script (Unknown) on this Behaviour is missing!” warnings are logged
Reproduced with: 1.3.7 (2022.3.4f1)
Not reproduced with: 1.1.33 (2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a22), 1.3.5 (2022.3.4f1), 1.3.7 (2021.3.28f1, 2023.1.3f1, 2023.2.0a22), 2.0.1-pre.18 (2021.3.28f1, 2022.3.4f1)
Could not test with: 2.0.1-pre.18 (2023.1.3f1, 2023.2.0a22) (Package causes scripting errors)
Fixed in: 2.0.1-exp.1 (2022.3.4f1)
Reproduced on: macOS 13.3.1 (M1) (by reporter), Windows 11
Notes:
1. Samples are available from Test Framework version 1.3.2
2. The actual regression is in the Editor version but it could not be found due to inconsistent reproduction -> details are provided in the internal comments
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
- PropertyField with range attribute triggers change event when the value didn't change
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
Resolution Note (fix version 1.4.4):
This issue seems to be indirectly fixed by refactorings in UTF 1.4.4