note: MuseIDE is capable of general automation tasks, not just testing. Tests are now called Tasks, but the terms are used interchangeably in this tutorial.

Create a task

The first step is to create a task resource in the project:

add-test1.png

After creating the task, the task editor is opened.

A task contains a hierarchy (tree) of steps. The root step is always a group of other steps. New tasksalso contains a step that logs a message to the event log. It is there as an example, remove that step if you don't need it.

test1-created.png

Adding a step to the task

I start by selecting the root step and then adding an new step to open a browser:

test1-add-open-step.png

Then configure it to use the browser and provider that we created earlier. You can double-click a step to edit it.

test1-configure-open-step.png

Editing a step initially starts out with the Inline Step Editor that uses a simple expression language to quickly configure parameters for a step. There is also a simple point-and-click editor as well as an expert mode - these are all explained on the Step Editor page.

In this case, the parameters reference the chrome-any and local-provider project resources that we created in the previous section of the tutorial. The format for these expressions is #"resource_id". I will cover more of these expressions in later sections.

Add more steps

Next, I want the browser to load a page, so add and configure a Goto Url step:

test1-goto-url-step.png

You can add a step to close the browser at the end of the task. This is optional - Muse will automatically do this when the task ends.

test1-close-browser-step.png

Step through the task

Use the Play or Step buttons to step through the task. Try stepping through to watch how each step executes. The event log shows detailed information about the execution of each step.

test1-run.png

Note that entering and exiting a compound step (such as the root step of every task) is a distinct action and requires a push of the Step button.

After the task finishes (or you stop it), the editor remains in run mode until you reset the editor. This allows you to inspect the task state and event log before clearing the editor.

test1-reset-editor.png

With a basic task working, I'm ready to interact with elements on the page.

Return to Tutorials page