Migrating from Mugnsoft IDE
Mugnsoft Pulse succeeds the Mugnsoft IDE browser extension. This page explains what changes and how to bring your projects across.
What changes
| Mugnsoft IDE | Mugnsoft Pulse | |
|---|---|---|
| Delivery | Extension for Firefox and Chrome | Portable application for Windows and Linux |
| Installation | From the browser extension stores | Extract an archive, no administrator rights |
| Saving projects | Downloaded as a file each time | Saved to and reopened from disk |
| Running journeys | Replay only | Replay, scheduling, thresholds, notifications, performance history |
| Deploying to Mugnsoft | Mugnsoft webserver and GitLab | The same, with several environments (production, pre-production…) |
Mugnsoft IDE is superseded by Pulse and is no longer the recommended way to build journeys.
Bring your projects across
Pulse uses the same .side project format.
- Install Pulse and activate a license.
- In the project picker, click Load Project and open your
.sidefile. - Replay every test, and fix the steps Pulse reports.
- Save the project.
The free tier allows 3 tests per project: a larger IDE project opens, but you need a paid license to add tests or to schedule suites larger than your limit.
Commands to replace
Some IDE commands do not exist in Pulse. Replace them before you replay or deploy a test:
| Mugnsoft IDE | Mugnsoft Pulse |
|---|---|
end transaction |
stop transaction, with the transaction name as Target |
log event |
start transaction — see Transactions |
choose ok on next confirmation, webdriver choose ok on visible confirmation |
accept confirmation, after the confirmation is shown |
choose cancel on next confirmation, webdriver choose cancel on visible confirmation |
dismiss confirmation |
answer on next prompt, webdriver answer on visible prompt |
answer prompt |
choose cancel on next prompt, webdriver choose cancel on visible prompt |
dismiss prompt |
submit |
click on the form’s submit button |
The IDE’s decrypt string, auth, click OK PopUp and uploadFile commands are not available in Pulse. For credentials, use the Key Vault or the encrypted passwords described in EUM Monitor when you deploy.
Deploying again
The Mugnsoft and GitLab connections are not imported from the IDE: enter them again in Runtime settings. The webserver API token and the GitLab token of the IDE can be reused while they are valid.
Monitors already deployed from the IDE keep running in Mugnsoft: moving to Pulse does not change them. To change a definition stored in GitLab, deploy it from Pulse with the Update action.
See also
- Overview — a tour of Pulse
- Commands — the commands available in Pulse
- Deploy to Mugnsoft — deploy tests from Pulse