M-RUN via VNC some character not tiped
Home › Forums › Ask Expert › M-RUN via VNC some character not tiped
- This topic has 4 replies, 2 voices, and was last updated 1 year, 7 months ago by Sasha ZAP.
-
AuthorPosts
-
October 5, 2022 at 2:49 pm #43646Marco MalziottiParticipant
It would seem that through the connection via VNC Agent ZapTest fails to write characters like “@”.
I attach:
– video: M-RUN via VNC.mp4 (see time 17″),
– connection files (masked ip): tester via vnc agent – ParmaCarSharing.mrc,
– data source: dt-cb-login.csv
– script: CB BA – login.zap
– report: Results – …2 01-57-24.zip
I also tried via Remote Desktop (scripthost: <ip>:3389, Username: <username-for-rdp-login>, password: <password-for-rdp-login>), obtaining “connecting.png” result.
Thank you.Marco Malziotti
P.S. Shared forder at : https://octospa-my.sharepoint.com/:f:/g/personal/m_malziotti_octotelematics_com/Eh785FgKkDNOh7TAl7JDnjIBN1atcHWDYb_HNEoP8mi8eg?e=qyHkRd (expire
Oct 11 2022)October 5, 2022 at 3:13 pm #43647Marco MalziottiParticipantLocal 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 versionOctober 5, 2022 at 3:42 pm #43648Sasha ZAPModeratorHello 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 TeamOctober 6, 2022 at 7:03 am #43655Marco MalziottiParticipantIf 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
October 7, 2022 at 5:49 am #43656Sasha ZAPModeratorHello 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 -
AuthorPosts
- You must be logged in to reply to this topic.