HTML Report for UnitTest Results

Introduce an HTML format for UnitTest results to enhance readability and presentation.

1️⃣ Description of the idea

Introduce a built-in HTML output format for UnitTest results in IRIS. This enhancement would generate a structured, visually intuitive HTML report that summarizes:

• Test suites and test cases

• Pass/fail status

• Assertions and error messages

• Execution time per test

The HTML report would complement format and provide a more shareable and readable format

2️⃣ Who is the target audience?

Developers running UnitTests, generate the report and share with team

QA engineers reviewing test coverage and test results

3️⃣ What problem does it solve?

Currently, UnitTest results in IRIS are mainly accessible through the System Management Portal, making them inefficient for sharing with others. not user-friendly for quick manual review.

By adding HTML output the results become easier to interpret and present Reports can be shared or published without tool dependencies

4️⃣ How does this impact the efficiency, stability, reliability, etc., of the product?

Team Collaboration: Enhances communication of test outcomes across dev, QA, and business teams

Usability: Improves experience for users with this output formats

Efficiency: Saves time by allowing quick navigation through test results

5️⃣ Provide a specific use case or scenario that illustrates how this idea could be used in practice

When the QA or development team runs test cases on the system, they often need to share the results for review and debugging. Currently, sharing results requires manual formatting or parsing through raw output formats, which can be inefficient.

With HTML Output:
The test suite automatically generates a UnitTestResults.html file containing:

• A collapsible view of test suites and individual test cases

• Clear visual indicators for pass/fail status

• A timestamp and summary section

• Clickable stack traces for failed tests

This HTML report can be easily shared via email or hosted on an internal portal, making it accessible to developers, QA, and other stakeholders. It greatly speeds up debugging and enhances visibility across teams, improving collaboration and traceability in the testing process.