Runtime settings

In this section you will learn how to connect Pulse to your Mugnsoft webserver and GitLab, and set the recorder, email and appearance options.

Open Runtime Settings with the cog button (Settings) of the toolbar. It has five tabs; each tab is saved with its own button, and a dot on a tab shows unsaved changes.

Mugnsoft

The connection to the Mugnsoft webserver that receives the tests you deploy.

Environments

Keep one connection per environment — for example Production, Preprod and Dev — and pick the target environment when you deploy. Use the Environment list to choose the one to edit, New to create one from the current fields, and the buttons next to it to rename or delete it. The last environment cannot be deleted.

Connection details

Field	Content
IP or FQDN	The address of the Mugnsoft webserver
Port	The port of its web interface
Protocol	HTTPS · secure, or HTTP · not secure for a webserver without TLS
Personal Token	An API token of the webserver, sent as a bearer token

Create the token on the webserver as described in Create API tokens, and give it a validity that suits you: deploying fails once it has expired. Click Test Connection: Connection verified confirms Pulse can reach the webserver with this token. Then click Save Mugnsoft Settings.

Gitlab

To commit your tests to a GitLab repository, alongside or instead of Mugnsoft:

Field	Content
Username	Your GitLab user name
Project Name	The repository that receives the tests
GitLab URL	`https://gitlab.com/` or the address of your own GitLab
Personal Access Token	A GitLab token with the `api` and `write_repository` scopes

Click Test Connection, then Save GitLab Settings. A dedicated GitLab account for your monitor definitions keeps commits apart from personal work.

Setting

Recorder Settings

Mouse Over Delay (ms) is how long the pointer must rest on a clickable element, while recording, for a mouse over step to be recorded: 500 ms by default, from 0 to 5000. Higher values record fewer hovers.

Monitor Configuration in .side File

The monitor information you enter when deploying — name, schedule, browser, thresholds, tags, probes, notifications — is saved inside the .side file, so it travels with the test.

Turn on the switch to keep secret fields out of the file: Slack and PagerDuty tokens, Teams webhooks, the proxy password, the TOTP secret and the Key Vault keys. It reads Secrets excluded from .side file when on. Turn it on before you commit a project to GitLab or share it.

Click Save Recorder Settings.

SMTP

The mail server used for email notifications:

Field	Content
SMTP Server Name	For example `smtp.gmail.com`
SMTP Port	Usually 587, or 465 with SSL/TLS
SMTP Email User	The account that sends the emails
SMTP User Password	Its password
SSL/TLS	Turn on to connect to the mail server over SSL/TLS

Under Test SMTP Connection, enter a Test Email Address and click Send Test Email, then Save SMTP Settings.

Appearance

Choose the Theme Preference: Light, Dark, or System to follow the theme of your operating system.