When using MagicPod with multiple members, such as in a team, it is recommended to establish operational rules during the initial implementation phase. This page provides examples of such rules.
Creating and updating test cases
- Define a policy for creating test cases
- It is advisable to prioritize which test cases should be created. Start by preparing around ten test cases, then gradually increase the number while keeping the health score in the green zone.
- Avoid creating test cases for screens that are expected to undergo major changes.
- Define a policy for updating test cases
- Determine the timing for updating test cases when there are changes to screens or functions. To efficiently investigate the causes of test failures, it is helpful to set up a process where developers can share information about upcoming changes in advance.
- Record updates using the History feature
- Assign a reviewer, and make sure that all test case creations and updates are reviewed using the History feature.
- Establish rules for adding Comment and Blank line commands.
- Naming Rules for UI Elements
- Avoid unclear names such as “Area (3)” or “Button (1)” that do not indicate what the element represents. Use names that make it immediately obvious what each element is.
- Assign a reviewer, and make sure that all test case creations and updates are reviewed using the Branch feature and History feature.
- Define a policy for Creating Shared Steps
- Since login processes are used in multiple test cases, it is recommended to define them as Shared Steps.
- Some teams set specific conditions, such as creating a shared step when a sequence of five or more steps is used in at least two test cases.
Managing Test Cases
- Define naming conventions for test cases
- Decide what information should be written in the description field
- Set rules for organizing UI components
- Set rules for using labels
- Set rules for organizing folders
- Set rules for organizing branches
Scheduled run
- Share the test execution schedule within the team
- Create a dedicated user account for scheduled runs
- It is recommended to visualize available time slots for cloud devices and browsers.
- Set rules for sharing changes made to scheduled run settings
- This can prevent problems such as unintentional test failures as a result of another member changing the scheduled run settings.
Reviewing test results
- Clarify who will check the results of scheduled test executions and when
- It is recommended to set up Slack and email notifications.
- Reference: Notification of test results
- Decide how to handle flaky tests with unstable results
- For example, temporarily exclude them from the scheduled run by adding a “Flaky” label, or contact MagicPod Support
- Reference: Improving test stability
Collaboration with developers
- Establish a workflow that allows collaboration with application developers for investigating test failures and improving test stability
Organization and projects
- Define policies for permission management
- If you need to manage members by project, enable the permission management feature at an early stage.
- Establish rules for deleting users when they leave the organization
- [For enterprise plan users] Security can be enhanced by using organization-specific users and restricting access by IP address
- Reference: Enterprise Plan Features
Others
- Regularly check the health score, such as once a week
- It is also recommended to use the MagicPod Web API to send notifications via Slack or other tools.
- Decide how to onboard new team members