MagicPod Trial Guide – MagicPod Help Center

About the Trial Guide

This page explains the recommended flow and tasks for getting the most out of your MagicPod trial.

※ For information on signing up for a trial, please visit: Free Trial procedure

Who This Trial Guide Is For

Teams introducing a test automation tool for the first time
Teams without dedicated QA or test engineers, where automation is handled by developers, managers, or business teams
Teams that have previously attempted to adopt a test automation tool but stalled before completing the rollout

To get the most out of your trial, we recommend approaching it with the following goals in mind:

Verify that the tool and approach align with your organization's test automation objectives and expected outcomes
Identify any gaps or trade-offs in achieving your automation goals, and determine how to address or accept them

Preparation Before Starting Your Trial

Preparation is key before beginning a trial of a test automation tool.

Items to Prepare and Consider Before Your Trial

For example, discovering mid-trial that you don't have a test account, or that your environment's IP restrictions are blocking access, will eat into your valuable evaluation time. Prepare the following items in advance to make the most of your trial.

Test automation goals
- Your goals for automation
Trial planning
- Trial schedule (a sample is provided on this page)
- Primary point of contact and allocation of time for trial activities
Test creation and execution setup
- Coordination of the environment to be used during the trial (DEV, STG, etc.), including IP allowlist configuration if needed
- Preparation of test data
- Accounts for the application under test

Examples of Operational Points to Consider

We recommend going beyond simply verifying that the tool works, and actually walking through how your team would operate — specifically, who will review results and who will handle fixes. You don't need to have everything figured out before the trial begins, but it's a good idea to have a rough sense of what decisions will need to be made between the trial period and full adoption.

Who is responsible for creating and maintaining automated tests
How often automated tests will run, and what will trigger them
Who will review test results
Who handles subscription renewals, account provisioning and reviews, and information security-related tasks

What to Check During Your Trial

Below is a sample schedule for a two-week trial.

Day1:

Start your trial by verifying connectivity and confirming that your application under test launches correctly. For mobile apps, check whether the app can be launched on MagicPod's cloud devices. For web apps, verify that the application is accessible from MagicPod.

If you encounter any issues at this stage, please contact MagicPod Support. For details on how to reach us, see: How can I get help using MagicPod?

Once connectivity and launch are confirmed, focus on getting hands-on with MagicPod's core features — creating tests, running them, and reviewing results.

We also recommend that multiple people participate in the trial. Please click here to learn how to add members: Method of adding members to the organization/project

Day2-3:

Continue familiarizing yourself with the basic features while also investigating compatibility with your application under test. Verify that the UI elements you need to interact with or assert on in your test steps can be handled correctly in MagicPod.

If you find any elements that cannot be interacted with, or if questions arise as you work through the learning process, take the opportunity to reach out to support — it's also a good chance to get familiar with the inquiry process itself.

If needed, this is also a good time to configure execution on your local PC or device. The following help pages cover the relevant setup.

Day4-5:

Starting from Day 4, begin building automated tests against your actual application under test. Be careful not to try automating too many scenarios at once. Start by automating a single scenario and set it up to run on a scheduled basis at least once a day.

Once your first scenario is automated, try tackling slightly more complex interactions and assertions. Test elements on the screen that change dynamically, and explore MagicPod features such as data patterns, conditional branching, loops, variables, and shared steps to broaden your test-building skills and discover ways to improve efficiency.

We also recommend tracking the time and effort required to create automated tests at this stage. Records of the person-hours spent on automation while you are still getting up to speed with the tool can serve as a valuable baseline for future cost-benefit estimates and for demonstrating gains in automation efficiency over time.

Day6-9:

During Days 6–9, review the results of your daily scheduled runs and, when tests fail, investigate the root cause and make any necessary fixes. This cycle of activities is essentially what ongoing test maintenance and operations will look like after MagicPod is fully adopted. Use this time to develop a concrete picture of the team structure, role assignments, and test design practices that will enable you to keep maintenance overhead as low as possible.

Tracking failure rates and the time spent on maintenance during this period is also recommended, as this data will be valuable when estimating costs and benefits later on.

Day10:

If the trial has gone well through Day 9, you should have a solid sense of whether test automation with MagicPod is feasible for your needs, as well as a clear picture of what day-to-day operations would look like after adoption.

Use this final day to compile any internal reports or presentations needed for decision-making, and keep it as a buffer to address any outstanding items that still require investigation or follow-up.

※ If you need to extend your trial period, please contact the support team.

Need Help?

The MagicPod Help Center and support chat are available to you throughout your trial period. Don't hesitate to reach out whenever you hit a technical roadblock.