testNGretry失败的testcase只需要在xml中配置一个listener即可

问题情况                                                 

先说下问题情况&＃xff0c;最近在做testNG与selenium集成做自动化测试的问题。

因为如果将testNG做UI 测试的话&＃xff0c;很多情况下可能测试是失败的&＃xff0c;但是这些失败可能是一些其他的问题导致的&＃xff0c;可能是脚本的问题或者是网络环境不稳定导致的&＃xff0c;所以我们需要重新尝试运行这个失败的测试用例。

testNG倒是没有直接的retry testcase的功能&＃xff0c;不过它却提供了很多的接口&＃xff0c;我们可以实现这些接口来得到retry的效果。

在google上看到淘宝的QA项目组采用Ruby语言将testNG的源代码修改了retry的功能&＃xff0c;然后又重新build后这样做的。这是一个solution&＃xff0c;但是我不推荐。原因有两个&＃xff1a;

1&＃xff0c;修改的jar包是针对指定的testNG版本的&＃xff0c;所以如果我们需要体验testNG的新版本功能&＃xff0c;这个jar可能就需要在源码基本上重新build有点 不太合适&＃xff0c;详细地址是&＃xff1a;https://github.com/NetEase/Dagger/wiki/Retry-Failed-Or-Skipped-Testcases

2&＃xff0c;该种修改的方法只能使用在testcase级别上&＃xff0c;如果需要针对所有的testNG的testsuite都是用这种特性&＃xff0c;可能就需要每个testcase都表明他们是使用这个retry功能&＃xff0c;有点代码亢余。像这样在testcase中声明retry的类&＃xff1a;

import org.apache.log4j.Logger;
import org.testng.Assert;
import org.testng.annotations.Test;import com.hp.baserunner.RetryFail;
import com.hp.pop.DemoPage;public class DemoRun {private static Logger log&＃61;Logger.getLogger(DemoRun.class);&＃64;Test(retryAnalyzer&＃61;RetryFail.class)// 这里声明retry的类&＃xff0c;可以看到如果这样每个testcase可能都需要这样做&＃xff0c;代码是不是有点多啊 :(public void demoTest(){DemoPage dp&＃61;new DemoPage();dp.demoTest();}&＃64;Testpublic void demoTest2(){DemoPage dp2&＃61;new DemoPage();dp2.demoTest2();}
}

Interface IRetryAnalyzer   这个就是retrytestcase的一个接口&＃xff0c;然后impletment这个接口后实现相应的方法即可&＃xff1a;

package org.testng.util;import org.testng.IRetryAnalyzer;
import org.testng.ITestResult;import java.util.concurrent.atomic.AtomicInteger;/**
* An implementation of IRetryAnalyzer that allows you to specify
* the maximum number of times you want your test to be retried.
*
* &＃64;author tocman&＃64;gmail.com (Jeremie Lenfant-Engelmann)
*/
public abstract class RetryAnalyzerCount implements IRetryAnalyzer {// Default retry once.AtomicInteger count &＃61; new AtomicInteger(1);/**
* Set the max number of time the method needs to be retried.
* &＃64;param count
*/protected void setCount(int count) {this.count.set(count);}/**
* Retries the test if count is not 0.
* &＃64;param result The result of the test.
*/&＃64;Overridepublic boolean retry(ITestResult result) {boolean retry &＃61; false;if (count.intValue() > 0) {retry &＃61; retryMethod(result);count.decrementAndGet();}return retry;}/**
* The method implemented by the class that test if the test
* must be retried or not.
* &＃64;param result The result of the test.
* &＃64;return true if the test must be retried, false otherwise.
*/public abstract boolean retryMethod(ITestResult result);
}

所以从上面可以看出&＃xff0c;如果直接使用继承这个RetryAnalyzerCount 类还是省不少事&＃xff0c;直接就可以使用了。

Class TestListenerAdapter

IConfigurationListener, IConfigurationListener2, org.testng.internal.IResultListener, org.testng.internal.IResultListener2, ITestListener, ITestNGListener

上面的是另一个类实现了retry的操作的类。这里不使用。

我们今天所使用的是IRetryAnalyzer 接口的&＃xff0c;代码如下&＃xff1a;

package com.com.baserunner;import org.testng.IRetryAnalyzer;import org.testng.ITestResult;/**
* &＃64;author sumeetmisri&＃64;gmail.com
* &＃64;modify alterhu2020&＃64;gmail.com
* &＃64;version 1.0
* &＃64;category
*
*/public class RetryFail implements IRetryAnalyzer{private final int m_maxRetries &＃61; 1;private final int m_sleepBetweenRetries &＃61; 1000;private int currentTry;private String previousTest &＃61; null;private String currentTest &＃61; null;public RetryFail(){currentTry &＃61; 0;}&＃64;Overridepublic boolean retry(final ITestResult result){// If a testcase has succeeded, this function is not called. boolean retValue &＃61; false; // Getting the max retries from suite.// String maxRetriesStr &＃61; result.getTestContext().getCurrentXmlTest().getParameter("maxRetries");String maxRetriesStr &＃61; result.getTestContext().getSuite().getParameter("maxRetries");int maxRetries &＃61; m_maxRetries;if(maxRetriesStr !&＃61; null){try {maxRetries &＃61; Integer.parseInt(maxRetriesStr);}catch (final NumberFormatException e){System.out.println("NumberFormatException while parsing maxRetries from suite file." &＃43; e);}}// Getting the sleep between retries from suite.you can from the suite parameter String sleepBetweenRetriesStr &＃61; result.getTestContext().getSuite().getParameter("sleepBetweenRetries");int sleepBetweenRetries &＃61; m_sleepBetweenRetries;if(sleepBetweenRetriesStr !&＃61; null){try {sleepBetweenRetries &＃61; Integer.parseInt(sleepBetweenRetriesStr);}catch (final NumberFormatException e){System.out.println("NumberFormatException while parsing sleepBetweenRetries from suite file." &＃43; e);}}currentTest &＃61; result.getTestContext().getCurrentXmlTest().getName();if (previousTest &＃61;&＃61; null){previousTest &＃61; currentTest;}if(!(previousTest.equals(currentTest))){currentTry &＃61; 0;}if (currentTry try{Thread.sleep(sleepBetweenRetries);}catch (final InterruptedException e){e.printStackTrace();}currentTry&＃43;&＃43;; result.setStatus(ITestResult.SUCCESS_PERCENTAGE_FAILURE);retValue &＃61; true;}else{currentTry &＃61; 0;}previousTest &＃61; currentTest;// if this method returns true, it will rerun the test once again.return retValue;}}

还有一个lisetner需要加入到testNG的配置文件中&＃xff1a;

package com.coma.baserunner;import java.lang.reflect.Constructor;
import java.lang.reflect.Method;import org.testng.IAnnotationTransformer;
import org.testng.IRetryAnalyzer;
import org.testng.annotations.ITestAnnotation;public class RetryListener implements IAnnotationTransformer {&＃64;SuppressWarnings("rawtypes")&＃64;Overridepublic void transform(ITestAnnotation annotation, Class testClass,Constructor testConstructor, Method testMethod) {IRetryAnalyzer retry &＃61; annotation.getRetryAnalyzer();if (retry &＃61;&＃61; null) {//annotation.setRetryAnalyzer(RetryAnalyzer.class);annotation.setRetryAnalyzer(RetryFail.class);}}}

然后在testNG的xml的配置文件中如下配置即可&＃xff1a;

xml version&＃61;"1.0" encoding&＃61;"UTF-8"?>
DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name&＃61;"FirstSuite" parallel&＃61;"false" ><parameter name&＃61;"excelpath" value&＃61;"resources/TestData.xls">parameter><listeners><listener class-name&＃61;"com.com.baserunner.RetryListener">listener>listeners>

以上的配置方法没有任何问题&＃xff0c;唯一的缺陷是&＃xff0c;运行的时候testNG的报告中会将retry的testcase的次数也计算在内&＃xff0c;所以可能造成&＃xff0c;运行后的testcase数目不准确&＃xff0c;关于这个问题网上也有人在讨论&＃xff0c;可是一直都没有得到一个好的接解决。

最近觉得仔细看看testNG的源代码&＃xff0c;看看能不能修改下对应的testNG的报告。使得结果显示的testcase数据与实际的一致&＃xff0c;retry的testcase只计算最后一次运行成功的。

如果有结果&＃xff0c;再更新。。。。。。。