Support allure run level failure logs by hi-rai · Pull Request #59 · Hypersequent/qas-cli

hi-rai · 2026-03-23T13:15:05Z

This fixes https://github.com/Hypersequent/tms-issues/issues/2340

gemini-code-assist · 2026-03-23T13:15:43Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the Allure report integration by enabling the extraction and upload of run-level failure logs from Allure container files. This ensures that critical setup and teardown failures, which are not associated with specific test cases, are properly captured and reported. Additionally, the internal API client has been refined for better extensibility and request identification, and the codebase has undergone minor refactoring for improved structure.

Highlights

Allure Run-Level Failure Log Support: The Allure parser now extracts run-level failure logs from *-container.json files, specifically from failed or broken befores and afters fixtures. This enhances the reporting of setup/teardown issues not tied to individual test cases.
API Client Enhancement: The internal API client has been refactored to use a more generic withHeaders utility, allowing for custom headers. This change also introduces a User-Agent header with the CLI version for better request identification.
Codebase Refactoring: Parser files (allureParser.ts, junitXmlParser.ts, playwrightJsonParser.ts) have been moved into a new src/utils/result-upload/parsers subdirectory to improve code organization.
Version Update: The CLI version has been bumped from 0.5.0 to 0.6.0.
Documentation and Testing Updates: Documentation (CLAUDE.md, README.md) has been updated to reflect the new Allure container parsing capabilities, and comprehensive unit tests have been added to validate the extraction of run-level failure logs from Allure containers.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request introduces support for run-level failure logs from Allure reports by parsing *-container.json files, which is a valuable addition for capturing setup and teardown failures. The implementation is robust, including comprehensive new tests that cover various scenarios and edge cases. The pull request also includes helpful refactorings, such as generalizing the API header utility and making the CLI version a pre-computed constant. Documentation in both README.md and CLAUDE.md has been updated accordingly. Overall, this is a high-quality contribution with no issues found.

hi-rai · 2026-03-23T13:16:25Z

src/api/index.ts

+		withHttpRetry(
+			withHeaders(withBaseUrl(fetch, baseUrl), {
+				Authorization: `ApiKey ${apiKey}`,
+				'User-Agent': `qas-cli/${CLI_VERSION}`,


Added qas-cli/<version> user-agent header, which might help in debugging future issues

hi-rai · 2026-03-23T13:17:45Z

package.json

 {
  "name": "qas-cli",
-  "version": "0.5.0",
+  "version": "0.6.0",


Bumped version for run level logs support

hi-rai · 2026-03-23T13:18:11Z

README.md

 3. **Test case marker in name** - Marker in `name` field (same `PROJECT-SEQUENCE` format as JUnit XML)

-Only Allure 2 JSON (`*-result.json`) is supported. Legacy Allure 1 XML files are ignored.
+Only Allure JSON result files (`*-result.json`) are supported. Legacy Allure 1 XML files are ignored.


There is also Allure 3, so we shouldn't specifically mention Allure 2

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4db32dc4e6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-23T13:19:38Z

src/utils/result-upload/parsers/allureParser.ts

+		const fixtures = [...(container.befores || []), ...(container.afters || [])]
+		for (const fixture of fixtures) {


Skip test-scoped containers when building run-level logs

Allure container files are not run-global by default: the format describes a fixture container that points back to the affected test result(s) via children. This loop promotes every failed/broken before/after to runFailureLogs without checking whether the container belongs to one or more concrete tests, so a normal pytest function-scoped fixture failure will now be uploaded both on the testcase (from the matching *-result.json) and again as a run-level log. In suites that use per-test fixtures, that makes a single-test failure look like a run-wide outage.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-03-23T13:19:38Z

src/utils/result-upload/parsers/allureParser.ts

 	if (includeStdout && statusDetails.message) {
-		message += `<pre><code>${escapeHtml(stripAnsi(statusDetails.message))}</code></pre>`
+		message += `<p>${escapeHtml(stripAnsi(statusDetails.message))}</p>`


Preserve preformatted Allure failure messages

This changes statusDetails.message rendering for every Allure testcase from a preformatted code block to a paragraph. Multiline assertion messages and diff-style output are common in Allure reports; wrapping them in <p> collapses newlines and indentation, so failed tests that only populate message now lose most of their structure in QA Sphere. Keeping the previous <pre><code> formatting avoids that regression in debuggability.

Useful? React with 👍 / 👎.

worth checking

Message should be a small text summary, ideal for <p>. The documentation also confirms the same - the short text message to display in the test details, such as a name of the exception that led to a failure. The error detail should be in trace, which already uses <pre><code>

satvik007 · 2026-03-23T14:56:23Z

src/utils/result-upload/parsers/allureParser.ts

 	if (includeStdout && statusDetails.message) {
-		message += `<pre><code>${escapeHtml(stripAnsi(statusDetails.message))}</code></pre>`
+		message += `<p>${escapeHtml(stripAnsi(statusDetails.message))}</p>`


worth checking

Support allure run level failure logs

4db32dc

hi-rai requested review from ramilamparo, satvik007 and sirkostya009 March 23, 2026 13:15

hi-rai self-assigned this Mar 23, 2026

gemini-code-assist bot reviewed Mar 23, 2026

View reviewed changes

hi-rai commented Mar 23, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Mar 23, 2026

View reviewed changes

satvik007 approved these changes Mar 23, 2026

View reviewed changes

hi-rai merged commit acf0d8c into main Mar 24, 2026
14 checks passed

hi-rai deleted the dev/himanshu/allure-run-failure-logs branch March 24, 2026 05:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support allure run level failure logs#59

Support allure run level failure logs#59
hi-rai merged 1 commit intomainfrom
dev/himanshu/allure-run-failure-logs

hi-rai commented Mar 23, 2026

Uh oh!

gemini-code-assist bot commented Mar 23, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

hi-rai Mar 23, 2026

Uh oh!

hi-rai Mar 23, 2026

Uh oh!

hi-rai Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot Mar 23, 2026

Uh oh!

satvik007 Mar 23, 2026

Uh oh!

hi-rai Mar 24, 2026

Uh oh!

satvik007 Mar 23, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		const fixtures = [...(container.befores \|\| []), ...(container.afters \|\| [])]
		for (const fixture of fixtures) {

Conversation

hi-rai commented Mar 23, 2026

Uh oh!

gemini-code-assist bot commented Mar 23, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

hi-rai Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

hi-rai Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

hi-rai Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

satvik007 Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

hi-rai Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

satvik007 Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants