Search Issue Tracker
Active
Under Consideration for 3.0.X
Votes
0
Found in [Package]
3.0.13
Issue ID
RIDER-48
Regression
No
Rider Test Explorer does not run tests when they are generated with TestFixtureSource
Reproduction steps:
1. Open the attached “TestFixtureRiderIssue“ project
2. In the Project window, open the “Assets/Tests/TestScriptWithFixture” script using Rider IDE
3. In Rider, open Unit Test Explorer (Tests > Navigation > Focus Unit Test Explorer)
4. Run all tests
Expected result: All tests are successful
Actual result: “Tests/MyNamespace/TestScriptWithFixture” test was not run due to “The assembly for this test is not found…” error
Reproducible with: 3.0.24 (2021.3.30f1, 2022.3.10f1), 3.0.34 (2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0a9)
Reproducible on: macOS Sequoia 15.1.1 (M1 Max), Windows 11
Not reproducible on: No other environments tested
Note: Tested on Rider 2024.1.6 (#RD-241.19072.26) and 2024.3.2 (#RD-243.22562.171)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Lights on Renderer Features break when rendering at lower resolution with "Forward+" Rendering Path
- [Android] High GPU usage is reported when the device is rotated into landscape orientation and the application is Vsync bound
- Aspect ratio toolbar doesn’t have tooltip to display contextual help or information when hovering over it
- Particle System isn't playing in Play Mode when it's out of view in Scene view, Simulation Space is set to "World", and Culling mode is set to "Pause and Catch-up"
- [Android] GameObject not rendered when rendering is performed with the help of "BatchRendererGroup"
Add comment