Recommended Number of Steps

Recommended Number of Steps

In MagicPod, there is no strict upper limit on the number of steps per test case. However, to ensure efficient and easy-to-maintain test design, we recommend the following guidelines:

• Even if a shared step contains multiple individual steps, it is counted as 1 step (“1 shared step = 1 step”).
• In the Standard Plan, for the purpose of calculating the Number of test cases, any test with more than 300 steps is counted as 2 test cases (tests with more than 600 steps are counted as 3 test cases, and so on).

• For this calculation as well, one shared step is counted as 1 step (“1 shared step = 1 step”).

Why We Recommend These Limits

MagicPod recommends these step count guidelines for the following reasons:

• A high step count makes it more difficult to identify the cause of a test failure.
• Long test cases tend to mix multiple use cases, which increases the scope of impact when changes are made, making maintenance more complex.
• Test cases with a large number of steps are more likely to experience instability or delays in the device, the target application, or the test process.

※“The site contains a large number of UI elements” refers to a site, in browser testing, where UI components are densely packed (as shown in the example image).
In such cases, if the test uses many steps that do not involve server communication—such as “Check” commands—the system load remains relatively low, even if the step count is higher. Therefore, the recommended maximum is increased to 300 steps.

Test Case Editor Performance

Currently, in MagicPod, if a test case contains a large number of shared steps, the performance of the test case editor may degrade—for example, it may take longer to load or save the test case.

We are aware of this issue and are working to improve it.
If you would like to receive a notification once the issue is resolved, please vote here.