With cloud-based test authoring, the mabl agent works autonomously in the cloud to build out your test, so you can focus more on what to test and not how to add steps or set up tooling.
When you start a cloud-based authoring session, the agents page tracks the progress of your test. Each session appears as a task with a real-time status and description of what the agent is working on.
Active and completed tasks
Sessions are organized into two sections:
- Active - tasks that are currently in progress or need your attention. Active tasks appear at the top of the page.
- Recently completed - tasks that have finished building or were stopped. Completed tasks appear below active tasks.
You can run up to 10 cloud authoring sessions at the same time. If you reach this limit, mabl prompts you to run the test locally instead.
Task statuses
Each active task displays one of the following statuses:
Working
The agent is actively building the test. No action is required. The agent displays a real-time description of its current activity.
Needs attention
The agent stopped because it couldn’t determine the next action. The task description explains what the agent needs.
To continue building the test:
- Open the test in the Trainer.
- Play the test up to the point where the agent couldn’t determine the next action.
- To get the test unblocked, either finish the remaining steps manually, or switch to Agent mode and play the agent.
Ready for review
The agent finished building the test. The task description includes a summary of how the session went. Open the test to review the generated steps.
Stopped
The session was stopped by a user. The task description identifies who stopped it and when.
Task details
To view more information about a session, click on the task to open its detail view. Task details include:
- The test name and a link to open the test
- A summary of the agent’s actions
- The current status and description
- A timestamp for when the build started and ended
RBAC permissions apply to viewing task details. For example, if a session used protected credentials that you don’t have permissions for, you can’t access that session’s task details.