#Vnc viewer port how to#

Run Selenium Standalone Debug Docker image

Map external VNC port to the Docker VNC port (5900): when you will run the docker image you will need to map the local VNC port to Docker VNC port (5900).

Any image that ends with -debug will have a VNC server installed

Use Selenium Debug images: to be able to see what's going inside the Docker container, you will need to use an image that has a VNC server installed.Install a VNC client: the one I am using in this tutorial is the RealVNC.But, with the help of the VNC viewer, you get a visual representation of exactly what's going on inside Docker which makes it easier to debug your test issues. Typically, when tests are being triggered inside Docker container, you are not able to see anything that's happening inside. However, the main reason we want to view tests in VNC viewer is to be able to debug any test issues that are happening inside the Docker. Because I thought the goal is to be able to view the tests running in VNC. Originally, when I was preparing this post, I was going to name the title 'View Selenium Tests in Docker using VNC Viewer'. Why run Selenium tests in Docker using VNC viewer?

We will also learn why it's important to run tests through VNC Viewer as well.

#Vnc viewer port how to#

In this tutorial, we will take a look at how to integrate VNC Viewer with Docker and debug Selenium tests in Docker using VNC Viewer.

In the previous post, we learned how to integrate Selenium tests with Docker.