Understanding test output messages

mabl lets users view their entire test output at once, but it's also helpful to be able to quickly and accurately identify the various messages that mabl includes in the test output feed. On this page you can find what each message means. mabl will also show you individual Journey steps as part of the view output

Visual Change

One of mabl's most useful features is her ability to detect changes between her original baseline test and the current test. You can swap between the current and baseline views to determine exactly what changed.

Sample view of filtering by visual changes.

Sample view of filtering by visual changes.

Error

When mabl fails to load a certain page, she will post an error message to the test output while still continuing through the test.

Sample view of filtering by errors.

Sample view of filtering by errors.

JavaScript Exception

When mabl detects a JavaScript error on the a page, she will log the type of error she encounters as well as the page and the source, if applicable.

Sample view of filtering by JS Exceptions.

Sample view of filtering by JS Exceptions.

Warning

When mabl encounters various non-working elements, such as broken links, she will log it in the test output page.

Sample view of filtering by errors.

Sample view of filtering by errors.

Info

This message simply describes to you, the user, what actions mabl is taking in your test. This will usually be your most common message.

Sample view of filtering by info.

Sample view of filtering by info.

Success

When mabl successfully completes major steps in your Journey, she will add these messages to your test output page.

Sample view of filtering by successes.

Sample view of filtering by successes.

Understanding test output messages


Suggested Edits are limited on API Reference Pages

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