...
To achieve this behavior, Qualitia provides an action called PressKeys, which allows specifying keys or key combinations in its parameter. To know the components of this PressKeys action, refer to PressKeys Actions.
You can execute the test cases on both active or inactive screen. An inactive screen is a screen that is minimized or is not visible when execution is happening. It is expected that all the steps in a test case must be properly executed even on the inactive screen. For example, while executing a test case with PressKeys on a VM and then switching to the local machine, the keys must be clicked on the VM (which has an inactive screen) where the test case is being executed.
...
The keyboard functionality can be automated in Qualitia Automation Studio, which internally uses the following ways for the implementation of PressKeys action:
Using Actions class provided by Selenium Web driver
...
When set to true, Qualitia internally uses the selenium web driver's Actions class to press keys. Selenium does not support some keys, which are mentioned in Using Actions class provided by Selenium Web driver.
References
https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/interactions/Actions.html
https://docs.oracle.com/javase/7/docs/api/java/awt/Robot.html
https://www.vbsedit.com/html/4b032417-ebda-4d30-88a4-2b56c24affdd.asp
...