SUT screen via VNC

When I connect into the SUT using Connection List, the window pops up showing the SUT screen. However, the desktop looks different and when I browse through the eggPlant Functional screen when it should be duplicates of the SUT, it looks that they are 2 different sessions.
If you move icons around on the desktop, and physically look at the SUT, the icons are not being moved around.

I was under the impression that when connecting via VNC and eggPlant Functional, we will get exactly duplicates of SUT screen. Is this not correct?

Thanks in advance for any help/suggestions.

Are you running against a Linux system? The default VNC server on Linux is actually an XServe implementation that creates an entirely new off-screen user session. There are VNC servers for Linux/Unix systems that are specifically designed to show display:0 (the logged-in user’s session), such as X11VNC and v5.x of the [url=]RealVNC Server for Linux.

Thanks so much for a prompt response.

Yes, I am using Linux. I installed TigerVNC, not knowing this.
Would you recommend switching to another VNC, or this should be fine for our testing purposes?


As long as you understand that you’re looking at an off-screen session and that everything you do to modify that session is going to have to take place over the VNC connection, it should be fine. Applications should run the same in that session as they do under the logged-in user. Be aware however that unless you have configured the server to provide persistent sessions, you will get a new user session each time you connect. This would be true even if the connection were temporarily lost and then restored during a script run.

There is an excellent writeup on using and configuring VNC servers on Linux here.

If I would like to keep the last session that I logged in (with windows open), which VNC would you recommend to install?

It’s less a question of which VNC server, than it is a question of how it’s configured. Any of the standard Xnvc implementations can be configured to provide persistent sessions. Or if you use one of the display:0 servers, then you’ll always get the desktop of the user logged in at the physical machine.