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
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
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 :/