Unable to find any test data conversion strategy for parameter with name ArrayList<XXX>-优快云博客

本文链接：https://blog.youkuaiyun.com/Derek_Zhang_/article/details/38731481

本文探讨了在使用EasyTest框架进行单元测试时，由于在Excel中重复定义测试方法名称而导致的一个具体问题。通过分析问题原因，文章提出了解决方案，并通过实例演示了如何避免此类错误。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

1. Problem

EasyTest

@RunWith(SpringTestRunner.class)
@DataLoader(filePaths = { "fixture/versionedBasRequests.xls" }, loaderType = LoaderType.EXCEL)
@ContextConfiguration(locations = "classpath*:applicationContext.xml")
@ActiveProfiles("test")
@TransactionConfiguration(transactionManager = "transactionManager")
@Transactional
public class BasRequestDaoTest {

	@Autowired
	private IBasRequestDao basRequestDao;

	@Test
	public void testGetCurrentVersionBetRequest(
			@Param(name = "ArrayList<BasRequest>") ArrayList<BasRequest> originalList,
			@Param(name = "targetBet") Integer targetBet,
			@Param(name = "currentVersion") Integer currentVersion) {

java.lang.AssertionError: Unable to find any test data conversion strategy for parameter with name ArrayList<BasRequest>and type class java.util.ArrayList
	at org.junit.Assert.fail(Assert.java:93)
	at org.easetech.easytest.annotation.Param$DataSupplier.getValueSources(Param.java:208)
	at org.easetech.easytest.internal.EasyAssignments.potentialsForNextUnassigned(EasyAssignments.java:100)
	at org.easetech.easytest.runner.InternalParameterizedStatement.runWithAssignment(InternalParameterizedStatement.java:109)
	at org.easetech.easytest.runner.InternalParameterizedStatement.evaluate(InternalParameterizedStatement.java:93)
	at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
	at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
	at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
	at org.easetech.easytest.runner.SpringTestRunner$1.evaluate(SpringTestRunner.java:376)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
	at org.easetech.easytest.runner.SpringTestRunner.runChild(SpringTestRunner.java:101)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
	at org.easetech.easytest.strategy.SerialScheduler.schedule(SerialScheduler.java:16)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
	at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
	at org.easetech.easytest.util.RunAftersWithOutputData.evaluate(RunAftersWithOutputData.java:111)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

2. Analysis

The cause is simple, I placed duplicated test method names in excel, and one of them had no test data. So the solution is obvious.