Checks

‍

The purpose of the software tests, besides compliance with the execution procedures, is to be able to control that the software complies with the expected behavior.

We will see what are the functions of Agilitest that allow to perform controls or assertions in your software tests.

Everything goes through the "Check" function.

This action comes in three sub-functions:

‍

• Check properties
• Check occurrences
• Check values

‍

"Check properties" and "Check values" will work the same way. The only difference is that in one case we will check the properties of one UI element and in the other the values of a variable.

“Check occurrences” will control the number of items counted in the displayed page of the tested software.

Check properties

This function takes as input an interface element that will have to be captured.

You can change the property name and the value that corresponds to it.

‍

You can select if the property is:

• Strictly equal
• Greater or equal
• Strictly Greater
• Lower or equal
• Strictly lower
• Different

Or use a regualr expression on the value below.

‍

Example :

In the example above, a SPAN is selected with an "id" equal to "cwos".

Its "text" property is verified to make sure it is equal to 4.

The verification function will perform the comparison considering both parameters as strings; and accepts regular expressions.

Check values

The operation is identical to the "Check properties" action described above. However, this function takes as input a variable which may or may not be modifiable.

You can have to select a value in order to compare it to the other one.

‍

You can select if the values are:

• Strictly equal
• Greater or equal
• Strictly Greater
• Lower or equal
• Strictly lower
• Different

Or use a regualr expression on the value below.

‍

Check occurrences

The occurrence check checks the number of elements found on the current page using an Agilitest locator, i.e. a targeted element.

‍

In some cases, it may be useful to define "locators" that can correspond to several elements. This can be used, for example, to control the number of rows or columns in a table.

The "Check occurrences"  action is also very useful to add robustness to your tests.

You can choose the number of occurences found.

You can select if the occurences are:

• Strictly equal
• Greater or equal
• Strictly Greater
• Lower or equal
• Strictly lower
• Different

‍

Check occurences and graphic recognition

Occurrence checking also works with graphical elements.

You will be able to check that an image is present a number of times in the displayed page.

This differs from a check based on the software structure, for example the DOM, for which even non-displayed items will be counted.

‍

You can also combine occurences checking and graphical recognition to determine when you will be able to continue your test.

‍

Security audit action 

The security and accessibility verification features in Agilitest, which are based on the open-source ATS (ActionTestScript) engine, include advanced analysis capabilities, with or without artificial intelligence.

The check-security action allows you to automate a basic security audit directly during the execution of functional tests.

From a script, select the Check action > Security audit

This action analyzes four categories of data on the current page:

• HTTP: Verification of headers (HSTS, CSP, etc…).
• Network: Detection of “mixed content” (unsecured resources on an HTTPS page).
• Console: Analysis of security errors reported by the browser.
• DOM: Searching for vulnerabilities in source code (e.g., inline handlers, sensitive attributes).

‍

Compliance levels and thresholds

The compliance level and the threshold are the two factors that will determine your security measures. 

These settings are configured directly in the Playlists, using the execution management menu.

‍

These checks are organized into three cumulative levels, based on security standards:

‍

• Level A (Critical): Detects major vulnerabilities (potential CSRF, GET requests with sensitive data, scripts in SVG files, etc.).
• Level AA (Important): Detects major vulnerabilities + Identifies significant weaknesses (password autocomplete, unsandboxed iframes).
• Level AAA (Enhanced): Detects the two levels above + Applies stricter hardening rules.

In summary, Level A will analyze critical errors; this is the highest level. The next two levels will also look for critical errors but will conduct more in-depth analyses and examine minor issues.

‍

You can also configure these parameters directly in the action with the "Override suite" button.

‍

AI use

You can choose whether or not to use AI when executing this action. This choice is specified directly within the script action. 

‍

To use AI in an action, you must first define an AI provider in the project properties.

‍

‍

Without AI, the action compares the page elements to a list of predefined, static rules. If the success rate falls below the configured threshold (e.g., 80%), the action fails.

With AI, this adds a layer of contextual analysis. It can determine whether a practice, while technically compliant with static rules, poses a risk in the specific context of the application (e.g., a suspicious input field that does not resemble a standard form).

‍

Case example: 

For an action defined at level AA and a threshold of 85%, the result may vary depending on whether or not AI is used.

For the same number of errors, the threshold might be 83% without AI and 85% with AI. This is because AI performs many more tests.

‍

Accessibility check (WCAG)

The Security RGAA / WCAG action in Agilitest is an advanced verification feature (powered by the open-source ATS-core engine) that allows you to automatically audit a web page for technical security and digital accessibility compliance.

‍

Click on the check action > Accessbility WCAG

‍

Exaclty like the security audit action (see above), you have a compliance level and a treshold for your action.

‍

These settings are configured directly in the Playlists, using the execution management menu or directly in the action.

You can choose whether or not to use AI when executing this action. To use AI in an action, you must first define an AI provider in the project properties (see above).

‍

Instead of verifying a single specific element, it performs a global page audit during execution. It looks beyond the visual aspect to analyze three technical domains:

• HTTP / Network: Checks for secure protocols (HTTPS), absence of "Mixed Content," and network call security.
• Console: Detects critical errors or information leaks in the browser logs.
• DOM (Document Object Model): Analyzes the HTML structure to detect vulnerabilities (like scripts in SVGs or unsandboxed iframes) or accessibility gaps.

‍

When you configure a Security / RGAA action, there are four options to act as filters or rule categories. They allow you to define which specific pillars of the accessibility and security standards you want the engine to audit.

‍

Each option corresponds to a different layer of the web page's code and user experience:

Visual: This option focuses on what the user sees and how information is presented graphically. It checks if the visual cues are backed by correct technical properties.

Interactive: This targets how the user behaves with the application. It focuses on navigation and input elements.

Semantic: This is the most technical part of the audit, focusing on the structure of the HTML (DOM).

Media: This option is dedicated to non-text content, such as images, videos, and audio.