Overview
In this section you will learn what Mugnsoft Pulse does and find your way around its main screens.
What Pulse does
Mugnsoft Pulse turns a user journey on a website into a replayable test. It uses the Selenium IDE project format: a project is a .side file that holds tests, suites and their commands.
With Pulse you can:
- Record a journey by using the site normally in the Pulse browser window
- Play back a test, or step through it one command at a time, at an adjustable speed
- Organize tests into suites and run a whole suite in one go
- Schedule suites to run automatically and keep a performance history for each test
- Notify your team when a scheduled run fails or crosses a threshold
- Deploy a test to Mugnsoft as an EUM monitor, commit it to GitLab, or export it as code
The features available depend on your license tier; see License activation.
How Pulse fits with Mugnsoft Core
Pulse runs and schedules journeys on its own, on the workstation where it is installed. When you need more than a workstation can offer — several locations, unrestricted frequency, alerting rules shared with the rest of your monitoring, reports and SLA — deploy the journey to Mugnsoft Core, where an EUM monitor runs it on your probes.
A typical workflow is:
- Record and fine-tune the journey in Pulse
- Replay it until every step passes reliably
- Schedule it in Pulse, or deploy it to Mugnsoft as an EUM monitor
- Follow its availability and response times in Pulse’s performance history, or in Mugnsoft
The project picker
When Pulse starts, it opens the project picker. Create a new project, load an existing .side file, or reopen a recent project. The badge in the top-right corner shows your license tier, and the version number is shown under the product name.
The Tests view
The Tests tab lists the tests of the project on the left. Selecting a test shows its commands, and selecting a command opens it in the step editor below the list, where you change the command, its target and its value.
The toolbar above the list plays the selected test, steps through it, starts recording and sets the playback speed. The right-hand panel is where the browser used for recording and playback appears; the width and height fields at the top set its size, and the log panel at the bottom shows the commands executed and any errors.
Hover over a test in the list to reach its actions: Performance History, Duplicate Test, Delete Test, Code exporter and Test Settings.
The Suites view
The Suites tab groups tests into suites. Select a suite on the left to see the tests it contains, and drag tests from Available Tests into it. Play Suite in the toolbar plays the whole suite.
Settings and guided tour
The cog button opens Runtime Settings: the Mugnsoft and GitLab connections, the recorder, SMTP for email notifications and the appearance (light or dark theme). See Runtime settings.
Start Guided Tour, next to it, walks you through the main screens inside the application.
See also
- Installation — download, verify and run Pulse on Windows or Linux
- Record your first journey — from an empty project to a passing test
- Migrating from Mugnsoft IDE — what changed since the browser extension