问题描述
与此处发布的解决方案类似，，我试图在onFinish（ITestContext上下文）中使用测试监听器删除（重复）测试结果。
Similar to the solution posted here TestNG retrying failed tests doesn't output the correct test results, I'm trying to remove a (duplicate) test result using a test listener during onFinish(ITestContext context).
尽管使用context.getFailedTests（）。removeResult（result）删除结果似乎工作正常（结果实际上已被删除），但似乎有其他一些点从中拉出结果导致构建仍然失败。
Although the removal of the result with context.getFailedTests().removeResult(result) appears to work fine (the result actually is removed), there seems to be "some other spot" where the results are being pulled from cause the build still fails.
还要注意，当我从上面的文章（有一个重复的失败被删除和一个通过测试）运行样本测试时，我得到了一个区别在测试结果（未按预期清理）与套件结果（重复故障按预期删除）中。
Also note that when I run the sample test from the article above (which has one duplicate failure to be removed and one passed test), I get a difference in "test results" (not cleaned up as expected) vs. "suite results" (duplicate failure removed as expected).
而且，报告从哪里获取结果以决定是否使构建失败？或者只是它在我清理失败的测试之前拉动结果......？
And, where is the reporting pulling the results from to decide whether to fail the build? Or is it just that it's pulling the results before I'm cleaning up the failed tests ... ?
===============================================
Default test
Tests run: 3, Failures: 2, Skips: 0
===============================================
===============================================
Default suite
Total tests run: 2, Failures: 1, Skips: 0
===============================================
编辑：为了澄清，我们正在使用maven运行这些测试，他们是IT ，所以我们使用failsafe插件运行它们。问题是，即使看起来测试被删除，mvn验证仍然无法构建，因为它认为无论如何都会发现构建失败。
Just to clarify, we're running those tests with maven, and they are ITs, so we run them with the failsafe plugin. The problem is that even though it appears that the tests are removed, mvn verify still fails the build as it considers build failures to be found regardless.
并且如果运行这样的话来自Eclipse的测试，即使测试被删除，套件完成后仍会在日志中打印失败。
And also if run such a test from Eclipse, even though the tests are removed, failures are still being printed in the log when the suite finishes.
关于RetryAnalyzer：我根本不会考虑使用RetryAnalyzer良好/最佳实践，但如果您发现自己处于需要解决问题的情况，例如你继承了一个依赖RetryAnalyzer的测试套件，你可能会觉得这很有用。
About RetryAnalyzer: I would not consider using RetryAnalyzer good/best practice at all, but if you find yourself in a situation where you need to solve the problem, e.g. you inherited a test suite that is relying on RetryAnalyzer, you may find this useful.
推荐答案
尝试使用这段代码：
ListenerApadter ：
public class MyTestListenerAdapter extends TestListenerAdapter {
@Override
public void onTestFailure(ITestResult result) {
if (result.getMethod().getRetryAnalyzer() != null) {
MyRetryAnalyzer retryAnalyzer = (MyRetryAnalyzer)result.getMethod().getRetryAnalyzer();
if(retryAnalyzer.isRetryAvailable()) {
result.setStatus(ITestResult.SKIP);
} else {
result.setStatus(ITestResult.FAILURE);
}
Reporter.setCurrentTestResult(result);
}
}
@Overrride
public void onFinish(ITestContext context) {
Iterator<ITestResult> failedTestCases =context.getFailedTests().getAllResults().iterator();
while (failedTestCases.hasNext()) {
System.out.println("failedTestCases");
ITestResult failedTestCase = failedTestCases.next();
ITestNGMethod method = failedTestCase.getMethod();
if (context.getFailedTests().getResults(method).size() > 1) {
System.out.println("failed test case remove as dup:" + failedTestCase.getTestClass().toString());
failedTestCases.remove();
} else {
if (context.getPassedTests().getResults(method).size() > 0) {
System.out.println("failed test case remove as pass retry:" + failedTestCase.getTestClass().toString());
failedTestCases.remove();
}
}
}
}
}
RetryAnalizer ：
public class MyRetryAnalyzer implements IRetryAnalyzer {
private static int MAX_RETRY_COUNT = 3;
AtomicInteger count = new AtomicInteger(MAX_RETRY_COUNT);
public boolean isRetryAvailable() {
return (count.intValue() > 0);
}
@Override
public boolean retry(ITestResult result) {
boolean retry = false;
if (isRetryAvailable()) {
System.out.println("Going to retry test case: " + result.getMethod() + ", " + (MAX_RETRY_COUNT - count.intValue() + 1) + " out of " + MAX_RETRY_COUNT);
retry = true;
count.decrementAndGet();
}
return retry;
}
}
POM.xml - > Surefire配置：
这是你应该配置覆盖具有自己的计数器的surefire监听器的地方。
This is where you should configure "overwrite" surefire listener wich has their own counters.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.18.1</version>
<configuration>
<suiteXmlFiles><suiteXmlFile>${basedir}/testng.xml</suiteXmlFile></suiteXmlFiles>
<properties>
<property>
<name>listener</name>
<value>Utils.MyTestListenerAdapter,Utils.MyRetryAnalizer</value>
</property>
</properties>
这篇关于通过测试监听器删除（复制）失败的TestNG结果的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！