Troubleshooting

In this section you will learn how to solve the most common Mugnsoft Pulse issues.

Installation

Extraction fails with “path too long”

The destination folder path is too long for the files in the archive. Extract it into a folder with a short path, such as C:\Mugnsoft, as described in Installation.

“Windows protected your PC” when starting Pulse

The archive was extracted with File Explorer without being unblocked first, so the extracted files kept the “downloaded from the internet” mark. Either click More info then Run anyway, or delete the mugnsoft-pulse-<version> folder, unblock the archive and extract it again as described in Installation.

There is no “Run anyway” button

Your organization’s security policy blocks applications that are not signed with a code-signing certificate. Ask your IT team to allow Pulse; they can check that the archive is genuine with its GPG signature, as described in Verify the download.

The antivirus quarantines Pulse

Verify the GPG signature of the archive first, as described in Verify the download. If the signature is good, restore the file from quarantine or ask your IT team to allow it, and let Mugnsoft support know so the false positive can be reported to the antivirus vendor.

Pulse does not start on Linux (SUID sandbox helper)

On some Linux distributions, Pulse stops at start-up with a message about the SUID sandbox helper binary: the distribution does not let applications create their own sandbox. Give the sandbox helper shipped with Pulse the rights it needs, once, from the Pulse folder:


cd ~/mugnsoft-pulse-1.2.0
sudo chown root:root chrome-sandbox
sudo chmod 4755 chrome-sandbox
./mugnsoft-pulse

Do it again after each update, in the new folder.

License

“Mugnsoft Pulse could not reach the license server for more than 14 days”

A paid license must reach the license server at least once every 14 days. Connect the computer to the internet, making sure a proxy or firewall does not block the Mugnsoft license server, and restart Pulse. See Offline use.

“Your license has expired”

The license reached its expiry date. Renew it, then enter the new key in Mugnsoft Pulse → License Management.

“License validation failed”

The license server rejected the license: it was revoked, deactivated for this computer, or the license file was modified or copied from another computer. Enter a valid key in License Management. Contact Mugnsoft support if you believe the license should be valid.

Usage

The play and record buttons are missing

The Tests toolbar is hidden while a suite is scheduled, so that manual runs do not interfere with scheduled ones. Turn off the schedule of the suite to get the toolbar back. See Scheduling.

I cannot create more tests

Your license limits the number of tests in a project; the free tier allows 3. Creating tests is also disabled while a suite is scheduled. Delete unused tests, turn off the schedule, or upgrade your license. See License tiers.

A suite cannot be scheduled

Only one suite can be scheduled at a time, a suite can only be scheduled if it contains no more tests than your license allows, and free licenses can only schedule suites hourly. Turn off the schedule of the other suite, reduce the number of tests in the suite, choose an hourly schedule, or upgrade your license.

A test passes in Pulse but reports “skipped”

The test contains desktop-application commands, which Pulse does not run locally. A run that skipped any of them is recorded as skipped rather than passed. See the note in Commands.

No notification is sent

Notifications are sent by scheduled runs only: schedule a suite that contains the test.
Check that the channel is on and at least one trigger is ticked in the Notifications tab of Test Settings, and use its test button.
For email, check the SMTP settings with Send Test Email.
With a free license, only email notifications are sent.

A test fails at full speed but passes step by step

The page is not ready when the next step runs. Add an explicit wait before the failing step — wait for element visible, wait for element present or wait for text — or record one with a right-click while recording. See Tests and steps.

Deploying to Mugnsoft fails

Open Runtime Settings → Mugnsoft and click Test Connection. If it fails, check the address, the port, the protocol (HTTPS or HTTP) and the token, which may have expired: create a new one as described in Create API tokens. A deployment that gets no answer from the server stops after two minutes with an error.