From 431a98a24d0f806899bb2bc55151856514d3fd29 Mon Sep 17 00:00:00 2001 From: Javier Re Date: Mon, 24 Jun 2024 10:37:52 -0300 Subject: [PATCH] Lippia Test Manager url update --- content/docs/cucumber/reporting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/cucumber/reporting.md b/content/docs/cucumber/reporting.md index 7b77b61f..67ad7d90 100644 --- a/content/docs/cucumber/reporting.md +++ b/content/docs/cucumber/reporting.md @@ -124,4 +124,4 @@ There are also many third-party plugins: * [Cucelastic](https://github.com/AshisRaj/cucelastic-maven-plugin) - Maven plugin to push test report data into Elastic Search to enable users to plugin UI agnostic tools like Kibana to visualize a dynamic and easy sharable report/dashboard with the possibility to filter and analyze the data, extend and share it across teams. * [cucumber-reporting-plugin](https://gitlab.com/jamietanna/cucumber-reporting-plugin) - A Cucumber plugin which produces pretty HTML reports using [cucumber-reporting](https://github.com/damianszczepanik/cucumber-reporting) * [Serenity/JS](https://serenity-js.org/handbook/integration/serenityjs-and-cucumber.html) - An acceptance testing and reporting framework with in-depth HTML reports, Screenplay Pattern APIs, and support for every single version of Cucumber.js -* [Lippia Test Manager](https://lippia.io) - Lippia Test Manager combines the use of Gherkin to support manual and automated test runs using Cucumber. It allows users to write tests in the Gherkin language without needing an integrated development environment (IDE) and to store them in code repositories, eliminating the need for mapping between manual and automated scenarios since it utilizes the .feature files. See samples of ingesting automated tests results here: [https://github.com/crowdar/](https://github.com/crowdar/) +* [Lippia Test Manager](https://lippia.io) - Lippia Test Manager combines the use of Gherkin to support manual and automated test runs using Cucumber. It allows users to write tests in the Gherkin language without needing an integrated development environment (IDE) and to store them in code repositories, eliminating the need for mapping between manual and automated scenarios since it utilizes the .feature files. See samples of ingesting automated tests results here: [https://github.com/lippia-io/](https://github.com/lippia-io/)