Search Issue Tracker
Fixed
Fixed in 1.4.5
Votes
0
Found in [Package]
1.1.33
1.3.2
1.4.2
Issue ID
DSTR-763
Regression
No
UnitySetUp is re-run if Domain Reload or enter PlayMode is triggered in more than one consecutive test
Reproduction steps:
1. Open the attached project “UnitySetUpIssueTestProject”
2. Open the Test Runner window
3. Select the first two or the last two tests
4. Right-click and select “Run Selected”
5. Observe the logs of the second selected test
Expected result: “UnitySetUp” is logged once
Actual result: “UnitySetUp” is logged twice
Reproducible with: 1.1.33 (2020.3.45f1, 2021.3.18f1, 2022.2.6f1), 1.3.2 (2023.1.0b3, 2023.2.0a1)
Could not test with: 2.0.1-pre.12 (2023.2.0a1) (error CS0619)
Reproducible on: macOS 12.4 (Intel)
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
- Editor Perforce login fails when Perforce shows a license expiry warning
- Assertion failed error in HDRP builds when enabling STP via script
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
- FileUtil.CopyFileOrDirectory throws IOException when destination parent folder does not exist
Resolution Note (fix version 1.4.5):
The issue with extra invocation of UnitySetup after domain reload is fixed in 1.3.3. Note that there is an issue where the output of tests would be repeated after a domain reload, effecting only the output inside the test results. This is fixed in 1.4.3