Search Issue Tracker
Won't Fix
Votes
4
Found in [Package]
1.14.0
1.15.0
Issue ID
ISXB-1561
Regression
Yes
UI Selectable's OnClick/Submit event is not triggered when using InputTestFixture with a mock keyboard in Test Runner
Reproduction steps:
1. Open the attached “IN-102384.zip” project
2. Open the Test Runner Window (Window > General > Test Runner)
3. Select the Playmode tab
4. Select 'Game Grumps - Joint Justice > PlayModeTests.dll > Tests > PlayModeTests > Suites > Playthrough > Case1 > TestSuite > NarrativeScriptsRunWithNoErrors > 1-4-JoryWitnessTestimony' test
5. Click “Run Selected”
6. Observe the Game view
Expected result: The test fully runs and finishes
Actual result: The test gets stuck when presented with two choices - 'Object!` and `Nah, we gucci`
Reproducible with: 1.1.0-preview.2 (2022.3.4f1), 1.1.1, 1.14.0 (2022.3.62f1, 6000.0.50f1, 6000.1.6f1, 6000.2.0b4)
Not reproducible with: 1.0.2, 1.1.0-preview.1 (2022.3.4f1)
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: No other environment 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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Actuating input via InputTestFixture has indeed unintentionally been broken in 1.1.0-preview.2, if updating from 1.1.0-preview.1. However, in the recent versions of the package, it's again possible to use InputTestFixture. While the customer project in report won't automatically work in the newest versions, unfortunately, it should still be possible to tweak it to work as we now have tests verifying the InputTestFixture stuff.