Question Simulate using mouse input doesn't working

I have a simple script to simulate left button mouse input like this:

Code (CSharp):

1.  
2.             _input.Move(Mouse.current.position, eventButton.GetComponent<RectTransform>().RectTransformToScreenSpace().position, queueEventOnly: true);
3.             InputSystem.Update();
4.  
5.             Debug.Log("Mouse pos room test: " + Mouse.current.position.ReadValue());
6.  
7.             _input.Click(Mouse.current.leftButton);
8.             InputSystem.Update();

but for unknown reason the button won't get clicked. Is there anything that I missed in that script?

 

Hey @Ali_Akbar_Montazeri !

Could you give more information about what are you trying to test?

I have been studying Integration tests in Unity in the last 2 weeks, maybe I can help you to setup a better workflow.

But for your question:

Click 

method call under the hood the

PressAndRelease 

method and probably you will need to use InputActionTrace to check if the mouse click was executed:

ref.: https://github.com/Unity-Technologi...sts/TestFixture/InputTestFixture.cs#L459-L462

Code (CSharp):

1. [UnityTest]
2.     public IEnumerator NewTestScriptWithEnumeratorPasses()
3.     {
4.         var pressAction = new InputAction("Press", binding: "<Mouse>/leftButton");
5.         pressAction.Enable();
6.  
7.         using (var trace = new InputActionTrace(pressAction))
8.         {
9.             Click(_mouse.leftButton, time: 0.2);
10.             InputSystem.Update();
11.  
12.             Assert.That(
13.                 trace,
14.                 Started(pressAction, _mouse.leftButton, 1, time: 0.2)
15.                     .AndThen(Performed(pressAction, _mouse.leftButton, 1, time: 0.2))
16.                     .AndThen(Canceled(pressAction, _mouse.leftButton, 0, time: 0.2))
17.             );
18.             trace.Clear();
19.         }
20.  
21.         yield return null;
22.     }

But I don't think this is the way to test behavior in your game.

 

It's kinda sucks that the button won't get clicked that way. So I've discussed with my team and found that

ExecuteEvents.Execute

is what we needed. It really does the click on the button