Create a mobile test outline with the mabl agent

Use the mabl agent to jumpstart test authoring. Read on to learn how to set it up for a mobile test:

• Define the intent of the test
• Launch the Trainer
• Build out the test
• Iterate as needed

Define the intent of the test

When you create a new mobile test, include a description of what you want the test to accomplish. Start with an existing test case or user story and augment it with an explicit description of the particular goals of the test.

While it's not necessary to describe every single click along the way, providing additional high-level details about the full end-to-end user journey can yield more successful results. For example, you can augment the description "buy Kindle on Amazon" with more details about who the user is and how they should complete the task:

"Verify an existing Prime customer can purchase an item.

Requirements:

• Use search bar to find item
• Item must be a Kindle
• Login using existing Prime account
• Verify checkout flow is successful."

Providing a test prompt

Launch the Trainer

After describing the intent of the test, fill out the remaining information on the test creation form and click on Create test. As the Trainer launches, mabl gathers information about the flows in your workspace, and the GenAI model uses this information to create an outline of your test.

The Trainer loads a set of generated steps, including tasks, flows, and visual assertions.

• Tasks - tasks are headers that break down the overall intent of the test into smaller goals
• Flows - if any existing flows are pertinent to the test case, mabl adds them to the relevant task.
• Visual assertions - each task finishes with a visual assertion to validate the expected behavior once a task is complete.

A test with mabl-generated tasks

Build out the test

Review each task in the Trainer and train any additional steps required to complete the task:

• Add steps
• Build out flows
• Complete visual assertions

Make sure your application is in the right state and the “Rec” button is on before you insert new steps.

Add steps

To add steps to a task, hover over the task and click on the Insert step button to place the Trainer cursor at that location.

Adding a step to a task

Build out flows

If the task contains a flow, you may need to train additional steps before or after the flow to accomplish the task. If the flow uses parameters, make sure the parameter values are properly configured.

To ensure mabl selects appropriate flows for your test, we recommend reviewing the existing flows in your workspace on a regular basis.

The following practices can help improve the overall quality of the flows:

• Use flow naming conventions
• Add echo steps, renamed steps, and assertions for readability
• Make sure flows target one specific purpose
• Remove redundant and unused flows

Complete visual assertions

Test the visual assertions to make sure they pass and generate appropriate criteria:

1. Click on the edit pencil next to the visual assertion.
2. Revise the assertion description if it is too vague or specifies inaccurate or irrelevant details.
3. Click on Test assertion to generate assertion criteria. Generating assertion criteria helps ensure the reliability of the visual assertion.

For more information on working with visual assertions, check out these articles:

• Creating visual assertions
• Best practices for visual assertions

Iterate as needed

Play back the test in the Trainer and iterate on this process as needed:

• Record any necessary steps that are not covered by the imported flows within each task.
• Revise visual assertions to make sure they pass and generate the appropriate criteria.
• If necessary, update the structure of the test by deleting, adding, or editing tasks.

To create a new task header, insert an echo step and add the special symbol “–>” before the text.