MoQuality

The MoQuality Developer Hub

Welcome to the MoQuality developer hub. You'll find comprehensive guides and documentation to help you start working with MoQuality as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Create a Test

A step-by-step example of using the Test Authoring Tool.

This guide gives a step-by-step example of creating a test using the Test Authoring Tool. In this example, you will create a new test that launches the browser application and executes a web search. Before starting, you must have created a project and uploaded an app. You must have also set up the Test Authoring Tool to connect to a local or cloud-based phone.

  1. Log in to MoQuality, open your project, and select the app you want to test.

  2. Click Create in the navigation bar on the left.

  3. Click Test to create a new Test. The Tests screen opens with an empty test loaded:
    2-EmptyTest

  4. In the status bar at the top of the Tests screen, make sure RECORD mode is selected, then connect to a phone from the Connect drop-down menu:
    3-StatusBarConnect

  5. Once your app launches in the browser, you are ready to create a new test:
    4-AppOpen

    The left column shows your app. The middle column lets you select actions and displays the UI hierarchy. The right column shows the steps as you add them to the test. For this test, you will open a browser and run a search.

  6. First, enter a name for your test in the top of the third column. Click the pencil icon; type the name of your test; then, click the check icon:
    5-NameYourTest

    Now add a step to your test that launches the browser.

  7. Select the browser icon UI element. Either click the browser icon on the virtual phone screen or select it from the UI hierarchy:
    6-SelectElement

    The Create a Step column updates to show details about the UI element and the actions you can apply to it:
    7-CreateStepDetails

  8. Review the Appium code at the top of the column and the UI Hierarchy in section 1. The code updates as you set the options in the Create a Step column.

  9. If you need to edit the reference to the UI Element, use the Select Filters section of the screen to focus the UI element selection:
    8-SelectFilters:

    Add and remove filters by selecting the hierarchy components that define the element you want to act on. You can add additional filters and UI elements by clicking the green + button.

  10. Choose an action in section 3. Select Click from the Touch dropdown menu:
    9-SelectTap

    Click on the Touch:Tap icon to collapse the menu. You can also add a timeout value and set other options depending on the action type in the Choose an Action section.

  11. Click the green Add button at the bottom of the Create a Step column to add that step to your test. A description of the step is added to the third column:
    10-StepAdded

    You can take several actions on a step: edit, run this step, run all steps starting from this step, and delete the step.

  12. Once the step is added, wait for the phone screen to update to show the results of the action. In this case, the browser opens:
    11-Browser

    Now, define a step that searches for "MoQuality".

  13. Select the search field UI element:
    12-SearchFieldUI

  14. Select Input in the Choose Action section and enter MoQuality in the text field:
    13-InputTextAction

  15. Click the green Add button. The step is added to the steps list.

  16. Now, add a step that executes the search. Use a Click action on the enter button on the keyboard.

  17. Finally, click the green Save Test button to save your test. Once you've saved you test, you can run it on any phone that you can connect to. Your test will show up in the list on the Tests page:
    14-testsList


What's Next

The following advanced sections will help you in creating tests

Selecting widgets
Create a step

Create a Test


A step-by-step example of using the Test Authoring Tool.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.