Minium Manager supports Java 1.8.

Minium Manager uses Selenium Video Node to run tests in parallel on multiple machines and manage different browser versions and browser configurations centrally.

The compatibility of Selenium Grid with Operating Systems are:

About the web browsers (based on the latest versions of the webdrivers), Selenium Grid supports:

You can check more details about the supported platforms at https://selenium.dev/downloads/.

Other providers are also supported:

Minium Manager web console is supported by the following browsers:

Minium Manager is currently localized in the following languages:

The following diagram shows the generic architecture of Minium Manager:

The main components of Minium Manager are Minium Manager, Jenkins for Continuous Integration in testing, Selenium Grid: one Hub (to monitor and manage the tests) and several Nodes (runs a browser to execute the tests). The number of nodes directly depends on the volume of executions and different browsers requirements for testing.

One of the standard installation for Minium Manager is:

This base configuration has two machines:

Minium Manager minimum requirements are:

Hard-Drive:

Memory:

CPU:

Other Requirements:

If the server machine is a LINUX system with no graphical interface. You will need to install the following packages:

Offline Server workaround:

If the server machine does not have Internet access, the RPM packages can be provided for RedHat family systems, then follow the steps below:

Local repository maven to execute the project will also be provided, then follow the steps below:

By default, Minium Manager uses an H2 database, but a MySQL database is recommended.

Before proceeding, it is necessary to create the database named minium.

Minium Manager uses Selenium Grid to provide an easy way to run tests in parallel on multiple machines and manage different browser versions and browser configurations centrally.

The default configuration run the Hub, and the Node in the same machine as Minium Manager, but it can choose to run the Hub and the Node on another machine or use the browserstack as provider to run the tests.

The quickest way to start using Minium Manager is to launch it as a standalone application.

An Alternative way to start using Minium Manager is through a docker container.

To run Minium Manager with docker, it is required have docker installed, docker compose too and a machine with Linux.

To install:

Minium Manager can be configured to export test results to TestLink. To configure the integration with TestLink, start by making sure the TestLink Plugin is installed on Jenkins. After that, go to Manage Jenkins > Configure System and configure the URL of TestLink, and a developer key with permissions to create builds on all the desired projects:

Then, open the config/application.yml and add the TestLink value to the minium.manager.modules property:

To log the batch update requests, configure the following logging levels:

Minium Manager supports new types of project: the monitoring project that are executed with high frequency (every 5, 10, 20 minutes), and can give us a report about the availability of a certain page and performance metrics, with the objective to check that the page are working as expected and Cookie Project that is two custom Minium Projects that generates a report with all browser cookies found during the navigation or crawl of a website.

Before configuring this new project type, first configure jenkins to add a new agent:

To add a new agent:

This chapter describes the procedure to gather all the information required to produce a valid license and how to set up the installation with a license. Minium Manager allows configuring Projects without a license but do not allow running tests without a valid license in place.

The license has a limit of executions per month. Each month, the execution number will reset. An alert will be shown in Minium Manager when the number of executions gets close to the limit.

As an example, if exists a project with 10 features and each feature have 5 scenarios, when an execution is launched in one browser it will consider 50 scenarios executed at the end of the execution. If launch the execution in 2 browsers, it will count 100 scenarios (2 x 50 scenarios) executed.

This chapter describes how to manage the logging of the several components of Minium Manager.

Configure e-mail reports for Minium Manager executions. This way, the execution’s status can be sent by e-mail, which is specially handy for large tests.

Before defining the e-mail recipients on the project configuration, configure the e-mail server.

To configure the e-mail gather the following properties:

This configuration is done on ./config/application-prod.yml as follows:

To use LDAP authentication, set the following properties in the config/application-prod.yml file:

Here is an example:

To record the tests and present the videos at executions and features pages, set the following properties in the config/application-prod.yml file:

Here is an example:

For the version of minium-cucumber-parent to be automatically updated for the projects have that auto-update enabled:

To print the errors at the console output, you need to add the error pattern (regular expression based in the java.util.regex package) that occurs in the console output of the child job (e.g. /ERROR: Subversion checkout has been canceled/). You can configure the patterns at the minium.manager.jenkins.error-patterns property list. When the pattern matches with a line at the console output of the child job, the console output will be added to the pipeline job until we find an empty line, or the line "Build was aborted". The error will be propagated to the pipeline job and will be printed at the front-end of Minium Manager. Example:

At front-end, Minium Manager displays a user-friendly message for the common cases: /org\.mozilla\.javascript\.JavaScriptException: Error: Module \".+\" not found\..*/ (Module missing at the project) and /org\.tmatesoft\.svn\.core\.SVNAuthenticationCancelledException: svn: E200015: Authentication cancelled/, /ERROR: Subversion checkout has been canceled/ (Wrong credentials for the scm repository).

When we detect errors of the type SCMInvalidCredentials, an email will be sent to warn the users (configured at the report section of the project’s configuration, if any).

To configure the Minium Manager to execute monitoring and cookie projects, set the following properties in the config/application-prod.yml file:

Here is an example:

Cookies

The Jenkins Node that will be executing the cookie projects needs the following environment vars:

To configure the NODE_PATH globally, you can define a path to your NODE_PATH environment variable (e.g. /opt/minium/crawler_dependencies/lib/node_modules/) and use the following commands to install the dependencies:

After, copy the file cookie-exporter.js at the bundle (located at ./tools/crawler/cookie-exporter.js) to the folder exporter of the node module headless-chrome-crawler (e.g. /opt/minium/crawler_dependencies/lib/node_modules/headless-chrome-crawler/exporter/cookie-exporter.js)

An executor allows a test execution to be executed and each executor can run ONE test execution at the time. In order to run parallel test executions, you need to choose an executor for each project.

Here is an example:

Additional WebDriver configurations can be set by adding profiles to the config/application-webdrivers.yml corresponding to the browser names and/or versions. Examples:

Since lacaixa have custom features in Minium Manager, they are separated in the property minium.manager.lacaixa.

At this property, we have the following configurations:

allow-scm-error

We have several configurations at this configuration:

Example configuration:

data-extraction-report-types

By default, the values configured are: DEFAULT and MONITORING.

The values allowed at this property are: DEFAULT, MONITORING, COOKIE_MINIUM and COOKIE_CRAWLER.

Minium Manager allow integration with HP Application Lifecycle Management (HP ALM). After Minium Manager execute the tests, the results are imported into HP ALM. Afterwards, see the results published in ALM.

Before configuring a project that imports the tests results to HP ALM, first configure the HP ALM Server at jenkins.

To configure e-the HP ALM Server at jenkins, edit the ./tools/jenkins/com.hp.application.automation.tools.settings.AlmServerSettingsBuilder.xml file to replace ${ALM_NAME} and ${ALM_URL} properties with the name of the ALM Server and the endpoint to the ALM Server, respectively.

If already launched Minium Manager (i.e. the folder ./data/jenkins/ already exists), edit the ./data/jenkins/com.hp.application.automation.tools.settings.AlmServerSettingsBuilder.xml file as well.

It is also required edit the ./config/application-prod.yml` as follows:

Launch Minium Manager and create/configure a project imports the tests results to HP ALM. The ALM properties can be found at the project properties by clicking at Advanced configuration button and selecting the ALM at Modules.

If using the embedded H2 database the database directory is removed by deleting the directory created by the extraction of the installation bundle minium-manager.zip.

If MySQL it is be used it is necessary to manually drop the database.

Finally, after everything else is removed, remove Minium Manager installation files by deleting the directory created by the extraction of the installation bundle minium-manager.zip.

Through the docker commands, remove the installed docker with the following command:

Finally, after everything else is removed, remove the Minium Manager configuration files by deleting the directory created by the extraction of the installation bundle minium-manager.zip.

To start the development of a monitoring project, you need to check the checkbox Is a Monitoring Project? to generate the monitoring project:

Here are some examples of the development workflow in Minium Developer of the monitoring project:

Since the Cookie Report project is a Minium project (based on the monitoring project), to create a Cookie Report project, simply generate a Monitoring project in Minium Developer. It is not necessary to add extra instructions to the minium code, since all browser cookies will be automatically extracted at the end of each scenario.

For the Cookie Crawler project, development is not necessary, you only need to provide one or more URLs to crawl.

To set up a project, click on the button New Project:

There are 4 project types we can select:

Then, fill the form:

Manage the access levels of the users/groups in the projects. It is also possible to add and personalize the level of access that assigns to each user or group, per-project.

In order to change the project permission the first step is go to the project configuration and click on tab Permissions.

Add user or groups to the permission table. Below the permission table, start typing the name of the user or group desired. Then click on the button Append.

After the users or groups was appended to the permissions table, define the permission for each entry appended and click Update to save the project configurations.

Labels were meant to be used only to filter projects in the Projects page providing a useful way to organize the projects.

Configuration profiles can be defined on the config/application.yml of a project and used to load configuration properties that vary based on the environment being tested. Such a configuration could be for example the URL of the application or the language:

These configuration properties can then be used on the step definitions like this:

Then to run test executions with the configuration properties of a profile, go to Project Configurations and add it to Additional profiles:

Sensitive configuration properties that cannot be included on the repository of the tests can be safely stored on Minium Manager. They can be used just like the configuration properties defined on the config/application.yml file of the project. As an example, consider that some tests need to be executed against a production environment which requires a password that cannot be exposed on the code. In that case, only the password to be used on the test environment would be defined on the config/application.yml file:

Which would be accessible through the config.password during the tests:

The password to be used on the production environment would then be defined on the Project Configurations:

We can add information of the test execution to the Minium Manager report by adding a simple minium instruction to the code of the Minium Project.

By add the minium expression scenario.write(…​); we are able to pass data to the Minim Manager report. E.g.:

The previous script will generate the following output in the Minium Manager console:

On the PDF report:

To delete a project, go to the project configurations and click on the button Delete Project, at the bottom-left corner:

To edit projects in batch, click on the button Edit multiple projects:

After the click, select the projects you want to edit and click on the button Edit selected projects:

After, you can edit the common properties of the projects in the modal:

After the changes, click Update Projects to save the changes ou Cancel to return to the projects page.

To stop the edit and deselect the projects, you can click Cancel:

To view the current queue of executions, click on the Project Queue under the navbar:

After the click, you can see the modal with the queue, with the projects Running and In Queue:

At the modal, we can also see the Scheduled Executions that will be executed in the future:

Also, the Executions History for the projects:

If the project is configured with the repository type File System, after the upload, we can edit the code of the Minium project.

The editor can be opened through several shortcuts:

At Project Configurations by clicking at the button Edit:

At Executions page by clicking at the button Edit, at the feature shortcuts (at web application testing project) and at the scenario and step shortcuts (at monitoring and cookie report project):

And at the Feature page, at the feature, scenario, step, and the links at the error message will have a shortcut to the editor:

After click on the button or the shortcut to the editor, a new tab will open with the code of the project.

In the editor, we can update the code of the minium project. after the changes, the editor can be closed.

To check the available browsers, click on Browsers, at the navigation bar.

In the figure above, we only have one provider available, but we can have two or more providers configured (e.g. "BrowserStack" and/or "Selenium Grid Extras"). The provider configured has the browsers Chrome, Firefox and Internet Explorer available.

This means that with this environment is able to run the tests in Chrome, Firefox and Internet Explorer at the provider configured.

Evolution chart to the test executions of a project.

Statistics for a single execution.

A test execution will execute the tests present in a project on one or more different browsers. There are alternative ways for launching test executions.

After launching a test execution, follow the progress in the project page. See the browser where the test is executing, the percentage, number of executed tests, the elapsed time and the test that is currently executing.

Overview of all the features, by clicking on the button View Feature.

View the result of each step in each browser that the feature ran.

Receive the reports of each test execution, in PDF and/or Excel formats, via email. Alternatively, download them directly in Minium Manager. To choose the formats to receive via email, go to the configurations of the project and expand the advanced configurations:

To download a report, expand the results of a test execution and click in Download report:

The daily report is a custom report with your favorite projects that will be sent to your email with the status of the last completed execution in the last 24 hours.

Before being able to configure a daily report, first you need to set the email configured at Account > Settings.

To create a daily report configuration, open the Account menu and click on Daily Reports.

Choose the projects to be included in your custom daily report:

After, schedule the time the email will be sent, with a summary of the past 24h.

Finally, click on the button "Create/Update Daily Report Configuration" to create/update the daily reports:

To delete the configuration, click on the button "Delete Daily Report Configuration".

The Data extraction report is a custom report (in Excel format) with your favorite projects that will be sent to the specified email addresses with the status of the last completed execution, and the project details.

To create and/or consult the data extraction reports configurations, open the Management menu and click on Data Extraction Report.

At the data extraction report page, you can see the current configurations created at the list Configurations.

You can edit (by clicking in the pencil button) or delete (by clicking on the trash button) the configurations listed at the list Configurations.

Also, you can create a new configuration by clicking on the button + New.

When you click the button + New, a form will appear (similar to the edit form) on the right side of the page:

To create a new configuration, fill the form by add a new configuration name (unique value), the emails that will receive the configuration, choose the projects to be included in the report and finally, schedule the time the email will be sent, with the report.

To save the configuration, click on the button + Save.

The email received will list a summary of the projects selected (separated by type), the statistics of the monitoring projects (How many executions since last report was sent, how many executions passed and how many executions failed), and will have the report (in Excel format) attached.

Minium Manager identifies the scenarios and features that were passing and in the last execution failed:

For monitoring projects, the executions page is:

At the mouse over in the warning icon, the regressions’s widget is presented to show more information about the past executions, the last execution passed, and the last execution failed for the regression:

The regression widget also allow adding comments at the regression detected. To add a comment, click ad + Add Comment and fill textarea and click Save:

After, we can check the comments added in the previous executions by clicking on the comment’s icon:

We can also edit the comment by clicking on Edit Comment:

Edit the text and click Save.

To delete the comment click `Delete.

To change the role of a user or group, navigate to Management > Roles at the navigation bar and:

Minium Recorder is already configured at Minium Developer Prime, but you can configure an existing Minium Recorder.

To configure Minium Developer with the Minium Recorder extension, first you need to download the Minium Recorder extension.

Navigate to the folder where Minium Developer is installed, create a folder named "extensions", copy the Minium Recorder extension file to the new folder and rename the file to "minium-recorder.crx".

After, edit the config/application-{windows,linux,macos}.yml file in order to add the following configuration (at the chrome webdriver):

Launch Minium Recorder through Minium Developer.

Open Minium Developer and add the following command to the editor:

This will load the google search engine website, when the instance of Chrome is launched.

To launch Minium Recorder, use the (Ctrl + Enter) shortcut or select Run > Launch Browser (1) and (2) at the top-right menu:

Select the Chrome browser (1), check if Minium Recorder is available (2) and click Created a new WebDriver (3):

A new instance of Chrome will be launched with the Minium Recorder extension installed. In the instance of Chrome, open the Developer tools by using the (F12) shortcut (use another shortcut) or select More Tools > Developer tools.

After the Developer tools of the instance Chrome is opened, select the Minium Recorder tab (1):

To start recording, click on the following button:

From now on, every interaction performed with the browser will be recorded.

For every action performed on the browser, like clicking on an element or filling a text input field, Minium Recorder will automatically generate the corresponding code. If typed an URL in the address bar, Minium Recorder will also generate the code to load that URL.

To try other expressions, click on the expression and a list of alternative expressions will be displayed:

To select an expression, just click on it.

Click on the pause button to stop a recording.

To import a script in Minium Developer, right-click on the editor area, where is intended to put the script, and choose the option Import recorded script: