1.7.165 - 2021/04/26

Release Notes

In addition to a number of smaller bugs and performance improvements that were resolved this week, there was one notable larger feature released:

🤙 Call Me, Maybe? Tell Me. Notify Me.

We didn't enable a Call Me feature. But, we did make notifications a whole lot clearer for batch test runs.

This helps keep your team on the same page as the status of a Quick Run, Full Run, or Specific Set of Device test runs. Look for it under the handy notifications bell in the Mesmer dashboard:

Screenshot of the Mesmer Notification bell located to the left of your Profile Avatar and Settings Icon.

We've included all the possible start triggers in the notification. This gives you the How and Who -- we leave the Why up to you :):

Invocation Methods

Run Type

CLI

Quick Run

Selected Devices

Web

Quick Run

Selected Devices

There are 4 types of notifications that we you can set your watch by:

🌀 Start Me Up.

Give it a spin. Unlike The Rolling Stones, if you start the bot up, it'll stop without making you cry. Now we'll let you know make it clearer when your well-timed test run started and where it's rockin' along.

🌀 Test Run Started at {startTime} - {numTests} tests by {userName} using {invocationMethod} on {deviceTypes}

🐳 Fail Whale. (aka, ⚠️ Execution Error)

Sometimes something doesn't quite start off on the right bot. Or, the bots have re-tried enough to know it ain't gonna without the help of a friendly human. This lets ya know.

⚠️ Error Encountered on Test Run Started at {startTime} - {numTests} tests by {userName} using {invocationMethod} on {deviceTypes}. The error encountered was {whateverErrorString}.

✅ Success!

We did it. Well, the bots did it! They successfully ran your test run. And, we'll tell you how long it took for the bots to do their thing.

✅ Test Run Completed in {totalMinutes} - {numTests} tests by {userName} using {invocationMethod} on {deviceTypes} completed at {endTime}.

🛑 Stop that Bot...

Sometimes you need to stop things before they started or stop them before they get out of hand. This let's you know when something ended and who may have stopped it along the way.

🛑 Test Run Started at {startTime} was Stopped by {userName} by Clearing the Queue - {testsStopped} / {numTestsStarted} tests were stopped by using {invocationMethod} on {deviceTypes}.

Watch for this feature will be enabled in the CLI and in a Webhook form in an upcoming release.

📌 Test Run Filters Now Persist

Another feature requested is that the filters set persist when switching screens, and when logging in and out. That was rolled out to everyone today. We know this will make life a little easier.

Recommended Tests

We has deprecated the Recommended Tests feature from the product as we revamp it for an upcoming release that'll make automated testing building much more faster and easier.