Skip to main content

ChainTest Reporting Framework (ExtentReports is being sunset)

 

ExtentReports is being sunset and will be replaced by ChainTest Reporting Framework.

1. What is ChainTest?

ChainTest is an open-source test reporting and analytics framework designed to enhance the way QA teams manage and analyze their test results. Think of it as a central hub for all your test data, offering:

  • Real-time analytics: Stay updated with the latest test outcomes.
  • Historical reports: Compare results over time to identify trends and improve processes.
  • Static reports: Easily share detailed HTML reports with stakeholders.
  • Multi-project dashboards: Consolidate data from different projects into a single view.

This tool is designed to integrate seamlessly into your existing testing workflows, providing both flexibility and scalability.

2. Why Use ChainTest?

Let’s talk about why ChainTest stands out:

  1. Enhanced Visibility: Gain clear insights into your test execution metrics, helping your team make informed decisions faster.
  2. Historical Analytics: Spot trends and recurring issues by comparing historical data.
  3. Effortless Reporting: Generate comprehensive reports in just a few clicks without relying on complex configurations.
  4. Easy Setup Options: Whether you’re using Docker for quick deployment or prefer manual setup, ChainTest adapts to your preferences.
  5. Open-Source Advantage: No licensing fees and the ability to customize the tool to suit your needs.

3. Set Up:

Part 1: Setting Up ChainTest

  • If you want a quick and hassle-free setup, Docker is the way to go. Simply run the pre-configured container and you’re good to go.
  • For those generating static reports only, you can skip Docker and set up the application locally by cloning the GitHub repo and following the instructions.

Part 2: Generating Reports

  • Upload your test data into ChainTest. The system supports integration with various testing tools.
  • Generate a static HTML report, which includes detailed metrics like pass/fail rates, execution times, and test case trends.
  • If you’re using the dashboard, explore real-time insights across multiple projects, compare results over time, and customize your views.

4. Key Use Cases

Here are some practical scenarios where ChainTest shines:

  • For Small QA Teams: Easily generate and share static reports without complex configurations.
  • For Enterprises: Use the dashboard to monitor multiple projects and gain insights from historical analytics.
  • For External Stakeholders: Share static reports in HTML format for clear and professional communication.

5. Getting Started

Here’s how you can start using ChainTest:

  1. Visit the GitHub repository at https://github.com/anshooarora/chaintest.
  2. Clone the project to your local machine using:
  3. git clone https://github.com/anshooarora/chaintest.git
  4. Follow the setup instructions provided in the documentation. Choose Docker for a quick setup or opt for the manual method for static reporting.
  5. Start generating reports and exploring the dashboard to enhance your QA workflows.

Pro Tip: If you’re new to the tool, check out the “Issues” section on GitHub for common questions or raise your own for support.

6. Closing

To wrap up, ChainTest is a game-changer for QA teams looking to streamline their reporting and analytics. Whether you’re working on a single project or managing multiple teams, this tool can help you save time, reduce manual effort, and improve overall test visibility.

If you’re intrigued, don’t wait – head over to the GitHub repo and start exploring today. And remember, it’s open source, so you can contribute to its development and make it even better for the QA community.

 

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);
Post a Comment
Read more