Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.4.3
Issue ID
DSTR-1039
Regression
Yes
All the tests with the same name as the selected test is run when they are in different assemblies
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Test Runner window (Window > General > Test Runner), enable “PlayMode” tests
3. Select the “ReportTestFramework1.4Bugs/SameNamespace.Subname.Tests.dll/SameNamespace“ test
4. Run Selected test
Expected result: Only the selected test was run
Actual result: Additionally to the selected test, the “ReportTestFramework1.4Bugs/SameNamespace.Tests.dll/SameNamespace“ test was also run
Reproducible with: 1.4.3 (2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 6000.0.0b14)
Not reproducible with: 1.4.2 (2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 2023.3.0b4), 2.0.1-pre.12 (2022.3.23f1, 2021.3.37f1)
Couldn't test with: 2.0.1-exp.1, 2.0.1-pre.12 (2023.2.17f1, 6000.0.0b14) (Test Framework throws a compilation error)
Fixed in: 2.0.1-exp.1 (2021.3.37f1, 2022.3.23f1)
Reproducible on: Windows 11, macOS 14.1 (Intel) (By user)
Not reproducible on: No other environments 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
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices to "2D Colour Attachment"
Resolution Note:
The test framework relies on the unique name of the tests to perform its filtering. The unique name is a combination of the namespace, fixture and method names. However, if the same namespace/fixture/method combination is present in another assembly, then it will see it as the same test.
We recommend using a top namespace that reflects the assembly name, ensuring that the type name of the test is unique.