Here, we shall describe the screens and terms for making the various settings.
1. User information
From Username▼ on the top right, you can configure email, API tokens, passwords, and accounts, as well as sign out.
- Email settings: You can change the email address for receiving test results emails, etc. For details, see Notification of test results
- API tokens: You can check the tokens used by the Web API.
- Account settings: You can change the username, GitHub account association, Two factor authentication (2FA) settings or language settings.
You can check the organization and the project.
If you click on the organization name, you can check the project and organization members, the usage situation, and the organization settings.
- Projects: You can confirm, add, and duplicate projects.
- Members: You can check and add members. For details, see Method of Adding Members to the Organization/Project
- Usages: You can confirm the number of test cases, and the number of visual diff steps.
- Settings: You can change the organization name, delete an organization, check or change the plan, and check the payment information.
If you click the project name, you can check test cases, test batch run, shared steps, project members, project settings, etc.
- Test cases: You can check, add, delete, copy, and sort.
- Batch runs: For details, see Running Batch Tests and Command Line Tests
- Common steps: For details, see Utilizing shared steps
- Settings: You can change the project name, delete projects, check and add test case labels, and set multi-lang data patterns. For details, see Running only specific test cases as a batch/Utilization of Multi-lang Data Patterns
5. Description of terms
Here, we shall explain some terms also introduced in 2. How to Create a Test.
- Organization Corresponds to one company. This is the unit of MagicPod contracts.
- Project This corresponds to one Web service.
- Test case This corresponds to one test scenario, such as “Member registration is successful” or “Charged registration procedures are successful.”
- Test This is the same as “test case”.
- UI This is the screen captured when creating a test.
- UI element These are items on the UI, such as input items, buttons, and pulldown options.
- Shared UI Use of the UI is shared amongst multiple test cases.
- Step One line of the test case
- Command Instructions run for each step of the test case.
- Run partial steps Run for only some steps of the test case. You can specify the scope using the blue bar displayed to the left of each step on the Edit Test Screen.
- Run each step test Run all steps for one test. You cannot run all the steps unless you end the element inspection mode.
- Batch run Run all steps within the project as a batch. You can perform a scheduled execution or run by specifying a special test case.
- Locator Character string for specifying UI elements operated at the time of the test (id, xpath, css selector, etc.) The user can add an original locator.
Next, we shall explain how to establish test automation practices in your organization in the fastest possible time.