GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — TestNG retries are marked as Skipped and the test itself is not marked as Flaky Test · Issue #452 · allure-framework/allure-java

TestNG retries are marked as Skipped and the test itself is not marked as Flaky Test #452

New issue
Copy link
New issue
Copy link
Open
Bug
Open
TestNG retries are marked as Skipped and the test itself is not marked as Flaky Test#452
Bug
Copy link

Description

@marvelfrozen
marvelfrozen
opened on Jun 18, 2020
Issue body actions

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

Tests that failed and then success after re-run using TestNG retryAnalyzer marked as skipped and not showing the Flaky Test (bomb) icon.
image
image

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

The retry impl class

public class RetryAnalyzerImpl implements IRetryAnalyzer {
	private int maxRetryCount = 3;
	private int retryCount = 0;

	public boolean retry(ITestResult result) {
		if (retryCount < maxRetryCount) {
			retryCount++;
			return true;
		}
		return false;
	}
}

The test method

@Test(retryAnalyzer= RetryAnalyzerImpl.class)
public void VerifyRetrievePublicaAndActiveCommunity(){
	int i = ThreadLocalRandom.current().nextInt(0, 2);
	System.out.println(i);
	Assert.assertEquals(i,0);
}

What is the expected behavior?

The retries are marked as Failed correctly. And the tests are marked as Flaky.

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

| Allure version | 2.13.3 |
| Test framework | [email protected] |
| Allure integration | [email protected] |
| Generate report using | allure windows [email protected] |

Other information

Activity

  1. baev
    added the
    Bug
    issue type on Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.