java 测试用例块,java – 编写Junit测试以覆盖异常和catch块

我已经为以下函数编写了Junit测试用例.当检查JACOCO测试覆盖率时.它显示只有try块被测试用例覆盖.我是编写测试用例的新手.如何在测试用例中涵盖异常和catch块

这是一种方法

public static List readCsvFile(String fileName)

{

BufferedReader fileReader = null;

//logic to read file

}

catch (Exception e)

{

System.out.println("Error in CsvFileReader !!!");

e.printStackTrace();

} finally

{

try

{

fileReader.close();

} catch (IOException e)

{

System.out.println("Error while closing fileReader !!!");

e.printStackTrace();

}

}

return students;

}

和TestMethod

@Test

public void ReadCsvFileTest()

{

String fileName = "test.csv";

List result = new ArrayList();

result = CsvFileReader.readCsvFile(fileName);

Student student1 = null;

Iterator it = result.iterator();

while (it.hasNext())

{

Student s = it.next();

if ("471908US".equals(s.getId()))

{

student1 = s;

break;

}

}

assertTrue(student1 != null);

}

解决方法:

在这种情况下,您可能经常考虑向您的班级引入其他依赖项.这是我粗略的例子.为读者创建工厂：

interface BufferedReaderFactory

{

public BufferedReader createBufferedReader(String fileName) throws IOException;

}

那么你将有一个简单的实现,几乎不需要任何测试,例如相似的东西：

class BufferedReaderFactoryImpl implements BufferedReaderFactory

{

@Override

public BufferedReader createBufferedReader(String fileName) throws IOException

{

return new BufferedReader(new FileReader(fileName));

}

}

然后你必须找到一种方法将这种依赖注入你的类.我通常在日常工作中使用Guice,但你可以尝试使用构造函数注入和使方法非静态的简单方法.这是一个例子：

class CsvFileReader

{

private final BufferedReaderFactory factory;

public CsvFileReader(BufferedReaderFactory factory)

{

this.factory = factory;

}

public List readCsvFile(String fileName)

{

BufferedReader fileReader = null;

try

{

fileReader = factory.createBufferedReader(fileName);

...

}

catch(IOException e)

{

...

}

finally

{

...

}

return new LinkedList<>();

}

}

使用像Mockito这样的模拟框架,这个类在IOException-s的情况下的行为现在更容易测试(请注意,您也可以返回从工厂抛出异常的模拟).这是一个示例：

@RunWith(MockitoJUnitRunner.class)

public class MyTest

{

@Mock

private BufferedReaderFactory mockFactroy;

@Test

public void testIOException() throws IOException

{

String ivalidFileName = "invalid.txt";

//throw exception in case that invalid file name is passed to the factory

Mockito.when(mockFactroy.createBufferedReader(ivalidFileName)).thenThrow(new IOException("Hello!"));

CsvFileReader csvFileReader = new CsvFileReader(mockFactroy);

//invoke with a factory that throws exceptions

csvFileReader.readCsvFile(ivalidFileName);

//...

//and make a sensible test here, e.g. check that empty list is returned, or proper message is logged, etc.

}

}

当然,你可以在没有Mockito的情况下做到这一点 – 通过实施测试工厂.但这更麻烦,尤其是在更复杂的用例中.一旦抛出IOException,您将获得JaCoCo的适当覆盖报告.

还要注意JaCoCo在here中提到的限制,在包含例外情况的源代码行中显示没有覆盖范围.为什么？

标签：java,unit-testing,spring,junit,junit4

来源： https://codeday.me/bug/20190828/1754769.html