Search Issue Tracker
Fixed in 1.1.2
Votes
0
Found in [Package]
2018.1.6f1
2018.2.0a1
2018.2.13f1
2018.3.0a1
2019.1.0a1
Issue ID
1092244
Regression
Yes
Test Runner does not run individual Test Fixtures
To reproduce:
1. Open attached project
2. Open the Test Runner window
3. Right-click on test fixture named 'Fixture Tests("Answer",42)' and select 'Run'
Actual results: Test don't run individually, first you have to run them all
Expected results: Tests named 'Test1' and 'Test2' in the fixture should both run
Reproducible with: 2018.1.6f1, 2018.1.9f2, 2018.2.17f1, 2018.3.0b11, 2019.1.0a10
Not reproducible with: 2017.2.4p2, 2017.4.16f1, 2018.1.5f1
Regressed version: 2018.1.6f1
Fixed: 2019.3.0b5 with Test-Framework 1.1.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
- Objects near the screen edge are not culled when using GPU Occlusion Culling
- InvalidCastException is thrown when hovering over a Tilemap with a saved Random Brush pick containing empty cells
Add comment