Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
Issue ID
1193636
Regression
No
[InputSystem] Cannot use InputTestFixture in a test script while using Input System package
To reproduce:
1. Open the attached project
Input System package is installed
Expected: No errors are thrown
Actual: Error is thrown: "The type or namespace name 'InputTestFixture' could not be found"
Reproduced with: 2018.4.12f1, 2019.2.10f1, 2019.3.0b9, 2020.1.0a11
2017.4 does not have the Input System package
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Added docs about the need for "testables" in https://github.com/Unity-Technologies/InputSystem/pull/1082.
Unfortunately for now, we have to live with this. Hopefully later, as the package system matures, we will have a more elegant solution for this :/