Broadly speaking, there are two ways of testing mobile websites using MagicPod. The first is to use Chrome's mobile emulation function to simulate test creation and execution. The other method is to run a test created using the mobile emulation function on a real device on an external Cloud. First, we shall explain the common test creation method (this does not currently support testing on a real device).
By setting the mobile device (smartphone, tablet) screen size and user agent using the mobile emulation on Chrome, it is possible to check behavior close to that of the mobile website. The advantage of this is that there is no need to launch a real device or a simulator/emulator, so the test can be performed both simply and quickly.
However, as it is not actually operating on the mobile device OS, the following types of detailed operations cannot be reproduced.
- Detailed differences in operation due to browser differences
- For example, if you are emulating the iPhone, the user agent will be Safari; however, since it will be operating on Chrome, it will not be able to find bugs specific to Safari.
- Differences in operation caused by the OS/hardware
In order to use the mobile emulation function, select “Mobile emulation (Chrome)” from “Device type” on the panel for selecting the browser, etc., and then choose the OS type and model. These models are taken from those currently provided in Chrome's developer tools, but you should contact MagicPod support if there is anything else you need to check.
State in which mobile emulation (Chrome) is selected
If you connect to the browser in this state, Chrome will open with the mobile-oriented display shown in the following figure. Other aspects can be operated in the same way as a normal desktop browser.
Chrome opened in mobile emulation mode
If the HTML on the site is the same, test cases created on websites for desktops can be run in mobile emulation mode and vice versa. Regardless of which mode the test cases were created in, the test will be carried out in the mode selected at the time of execution.
Refer to “Batch execution in a BrowserStack Cloud environment” or “Batch execution in a SauceLabs Cloud environment” for how to execute the created test on a real device (a separate service contract shall be required in either case).