MagicPodDesktop is the client software required to create and execute automated tests on your local PC. You can download it here.
This application plays a key role in your local testing environment by running tests directly on your machine, sending test data (e.g., screenshots, page source) to the MagicPod server, and retrieving necessary information from the server to execute tests locally.
Please refer to the technical configuration diagram below for a visual explanation.
Frequently Asked Questions
Do I need to update MagicPodDesktop every time a new version is released?
We recommend updating within 3 months after a new version is released. We strive to maintain backward compatibility for at least 6 months. (*This may not be guaranteed in some cases due to unavoidable changes from external sources.)
If your version becomes outdated and incompatible, you will see an error message. Please see this page for details.
Can I run a local test using MagicPodDesktop on a virtual machine (VM)?
Yes, you can run MagicPodDesktop on Windows and Mac virtual machines.
MagicPodDesktop cannot be used on Linux. However, it is possible to run tests with magicpod-command-line on Linux. (Reference: Supported environments)
Are there any PC performance requirements for running MagicPodDesktop (browser test)?
While we do not have official hardware recommendations, a PC with at least 8GB of RAM generally runs MagicPodDesktop smoothly for browser testing.
What is the difference between MagicPodDesktop and MagicPodConnect?
MagicPodDesktop runs tests using a browser on your local machine. It communicates with the MagicPod server by sending and receiving test-related data (such as screenshots and page source), but the actual web page under test is accessed locally.
MagicPodConnect, on the other hand, is used when the test browser is running in the cloud. It establishes a secure tunnel between your local environment and the MagicPod cloud, allowing access to internal or private web pages during cloud-based test execution. This results in different communication methods and connection endpoints compared to MagicPodDesktop.
Are Selenium/Appium servers included in MagicPodDesktop and running on a local PC?
Yes, the Selenium/Appium servers are included in MagicPodDesktop. The automatic operation of the browser and mobile devices is performed by Selenium/Appium on a local PC.
MagicPodDesktop is the relay between MagicPodDesktop and the MagicPod server and between Selenium/Appium.
When the test is run on MagicPodDesktop, a number of browser processes equal to the number of times the test was run remain on the local PC.
To help with debugging, MagicPodDesktop does not automatically close browser processes after test execution. If you are using a CI tool such as Jenkins, please explicitly delete the process by inserting a command such as “sudo pkill ${PROCESS_NAME}” into the job.
Can I run multiple instances of MagicPodDesktop at once?
Yes—but be aware that if you launch MagicPodDesktop on multiple devices using the same account credentials, tests may run simultaneously on all devices.
To avoid this, use a different MagicPod account on each device, and ensure separate login credentials are saved.