M-RUN via VNC some character not tiped
- This topic has 4 replies, 2 voices, and was last updated 2 years, 6 months ago by
Sasha ZAP.
Sasha ZAP.-
Posts
-
Marco Malziotti
Local host:
– Windows 10 Enterprise 64 bit
– ZapTest 22.5.4 version
Remote host (reachable with both remote desktop and VNC):
– Windows 10 Pro 64 bit
– TightVNC 2.8.59 version
– ZapTest Agent 2.0.0011 versionSasha ZAP
Hello Marco,
I’ve just ran your test several times on one of our remote machines using M-RUN and there was no problems typing characters such as the at (‘@’) character.
The only issue was that the object “Private profile” was not found because when I run the test it appears differently then in your GUI Map screenshot.
I’ve noticed there are different reasons why such character may not be typed in certrain machines – Please check in Google solutions to the subject “my browser cannot type the at character”.
Hope this helps.
Thanks,
ZAPTEST TeamMarco Malziotti
If I install ZapTest 22.5.4 version on the remote machine and run the test directly from there (without M-RUN) everything works.
Running the test from the local machine and running the test directly from there (without M-RUN) everything works.
Both are Windows machines and have Chrome version
– 106.0.5249.62 at local host.
– 106.0.5249.91 at remote host.
Thanks,Marco Malziotti
Sasha ZAP
Hello Marco,
I’ve forwarded your issue to our R&D Dept and once I’ll have an answer I’ll let you know.
I’m sorry for the trouble.
P.S. I understand you are still using the ZAPTEST Free Edition, correct? If yes then please check the Free Edition and Enterprise Solution comparison at:
Thanks,
ZAPTEST Team
Marco Malziotti
Sasha ZAP- You must be logged in to reply to this topic.
