-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
b86eb5e
commit 99105a9
Showing
10 changed files
with
853 additions
and
631 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| layout: default | ||
| title: "Healenium Integration" | ||
| excerpt: "Learn how to use Healenium inside your BELLATRIX tests" | ||
| date: 2024-07-04 16:40:00 +0200 | ||
| parent: product-integrations | ||
| permalink: /product-integrations/healenium/ | ||
| anchors: | ||
| what-is-healenium: What Is Healenium? | ||
| usage: Usage | ||
| --- | ||
| What Is Healenium? | ||
| ------------------ | ||
| **[Healenium](https://github.com/healenium/healenium)** is an open-source library designed to enhance automated testing frameworks by providing self-healing capabilities for Selenium-based tests. It helps maintain the robustness of test scripts by dynamically updating locators when they change, reducing the need for manual maintenance. | ||
|
|
||
| Usage | ||
| ------------------ | ||
| To use Healenium self-healing capabilities for your BELLATRIX Selenium tests, simply state in the config file, in the web section, as **executionType** "healenium". |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| --- | ||
| layout: default | ||
| title: "Jira Zephyr" | ||
| excerpt: "Learn how to integrate BELLATRIX tests with Jira Zephyr Plugin." | ||
| date: 2024-07-04 16:40:00 +0200 | ||
| parent: product-integrations | ||
| permalink: /product-integrations/jira-zephyr/ | ||
| anchors: | ||
| what-is-jira-zephyr: What Is Jira Zephyr? | ||
| usage: Usage | ||
| config: Config | ||
| --- | ||
| What Is Jira Zephyr? | ||
| ------------------ | ||
| The **[Jira Zephyr](https://smartbear.com/test-management/zephyr-squad/)** plugin is an add-on for Jira that enhances its capabilities for test management. Zephyr, integrated within Jira, provides tools for creating, managing, and executing test cases directly within the Jira environment. | ||
|
|
||
| Usage | ||
| ------------------ | ||
| When we have BELLATRIX tests which correspond to zephyr test cases inside jira and we want to automatically create test cycles when the tests are executed, the jira-zephyr plugin of BELLATRIX proves handy. | ||
|
|
||
| To use this plugin, we first need to import it to our test module. After that, we must register it. | ||
|
|
||
| ```java | ||
| @Override | ||
| protected void configure() { | ||
| super.configure(); | ||
| addPlugin(ZephyrPlugin.class); | ||
| } | ||
| ``` | ||
|
|
||
| We can annotate the test class with the ```@ZephyrProjectId```. | ||
|
|
||
| ```java | ||
| @ZephyrProjectId("BELLATRIX") | ||
| public class JiraZephyrTests { | ||
| // code | ||
| } | ||
| ``` | ||
|
|
||
| Then, we simply annotate our tests with their respective test case ids with ```@ZephyrTestCase```. | ||
|
|
||
| ```java | ||
| @ZephyrTestCase(id = "B-12") | ||
| @Test | ||
| public void testingJiraZephyrIntegration() { | ||
| // code | ||
| } | ||
| ``` | ||
|
|
||
| One can customize the plugin through the config. | ||
|
|
||
| Config | ||
| ------------------ | ||
| The settings section in the config file must look like this: | ||
| ```JSON | ||
| "zephyrSettings": { | ||
| "isEnabled": "true", | ||
| "apiUrl": "insert/the/url/of/the/api", | ||
| "token": "insert the token generated from jira zephyr", | ||
| "defaultProjectKey": "insert the default project's key to be used, if not defined in the test class or test case", | ||
| "isExistingCycle": "insert false to generate new test cycle, insert true and provide in the test class or test case the id of the existing test cycle", | ||
| "testCycleName": "insert the name of the test cycle to be created", | ||
| "cycleFinalStatus": "insert the final status of the cycle" | ||
| } | ||
| ``` | ||
|
|
||
| Mandatory settings are the ```isEnabled```, ```apiUrl```, and ```token```. If you define ```isExistingCycle``` as true, ```testCycleName``` may be omitted. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| --- | ||
| layout: default | ||
| title: "Twilio SMS Integration" | ||
| excerpt: "Learn how to test SMS using Twilio with BELLATRIX" | ||
| date: 2024-07-04 16:40:00 +0200 | ||
| parent: product-integrations | ||
| permalink: /product-integrations/twilio/ | ||
| anchors: | ||
| what-is-twilio: What Is Twilio? | ||
| usage: Usage | ||
| config: Config | ||
| --- | ||
| What Is Twilio? | ||
| ------------------ | ||
| **[Twilio](https://www.twilio.com/)** is a cloud communications platform that enables developers to build, scale, and operate real-time communications within their applications. Founded in 2008, Twilio offers various APIs to facilitate communication services, including voice, video, and messaging. | ||
|
|
||
| Twilio's SMS services are among its most popular offerings, allowing businesses to send and receive text messages globally. | ||
|
|
||
| Usage | ||
| ------------------ | ||
|
|
||
| The Twilio SMS API is exposed through an **SmsService** in BELLATRIX. To access it, you must include the bellatrix.sms module as a dependency. | ||
| **SmsService** class is an utility class and contains only static methods. Another class is **SmsListener**. | ||
|
|
||
| Here are some examples usages of the twilio integration in BELLATRIX: | ||
| ```java | ||
| var authenticationSmsListener = SmsService.listenForSms(fromNumber); | ||
| // code which will trigger an sms to be sent to the phone number you have specified inside the config file | ||
| var authenticationMessage = authenticationSmsListener.getFirstMessage(); | ||
| authenticationSmsListener.stopListening(); // we stop listening for messages as we have already received the message we need | ||
| ``` | ||
| We start listening for messages from the number we are expecting a message from, we wait for the message to be received and then we get it. | ||
|
|
||
| ```java | ||
| var allMessages = authenticationSmsListener.getMessages(); | ||
| ``` | ||
| Get all messages. | ||
| ```java | ||
| var filteredMessages = authenticationSmsListener.getMessage(m -> m.getBody().contains("code")); | ||
| ``` | ||
| Filter messages. | ||
| ```java | ||
| var lastMessage = authenticationSmsListener.getLastMessage(); | ||
| ``` | ||
| Get last message. | ||
|
|
||
| Config | ||
| ------------------ | ||
| The settings section in the config file must look like this: | ||
| ```JSON | ||
| "twilioSettings": { | ||
| "accountSID": "insert your account SID", | ||
| "authToken": "insert your auth token", | ||
| "phoneNumber": "insert the phone number which will be used by your tests" | ||
| } | ||
| ``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| --- | ||
| layout: default | ||
| title: "Visual Regression Tracker Integration" | ||
| excerpt: "Learn how to use Visual Regression Tracker inside your BELLATRIX tests" | ||
| date: 2024-07-04 16:40:00 +0200 | ||
| parent: product-integrations | ||
| permalink: /product-integrations/visual-regression-tracker/ | ||
| anchors: | ||
| what-is-visual-regression-tracker: What Is Visual Regression Tracker? | ||
| usage: Usage | ||
| config: Config | ||
| --- | ||
| What Is Visual Regression Tracker? | ||
| ------------------ | ||
| **[Visual Regression Tracker](https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker)** (VRT) is a tool used in software testing to detect visual changes in a web application's user interface. It captures screenshots of web pages and compares them with baseline images to identify any unintended visual differences. This is particularly useful for ensuring that updates or changes to code do not introduce visual bugs. | ||
|
|
||
| Usage | ||
| ------------------ | ||
| To use VRT inside your BELLATRIX tests simply add bellatrix.addons.visual-regression-tracker as a dependency. After that, you can use VRT to track the UI in specific points in your tests like this: | ||
|
|
||
| ```java | ||
| VisualRegressionTracker.takeSnapshot(name); | ||
| ``` | ||
|
|
||
| It will automatically take a screenshot and send it to VRT server for analyzing. | ||
|
|
||
| Config | ||
| ------------------ | ||
| The settings section in the config file must look like this: | ||
| ```JSON | ||
| "visualRegressionTrackerSettings ": { | ||
| "apiUrl": "insert your api url", | ||
| "project": "insert your project", | ||
| "apiKey": "insert your api key", | ||
| "branch": "insert your branch", | ||
| "enableSoftAssert": "true", | ||
| "ciBuildId": "insert your ci build id", | ||
| "httpTimeout": "10" | ||
| } | ||
| ``` |
Oops, something went wrong.