Update - commenters pointed out an obvious mistake - I should have kept the sample code here the same as my real code. I've updated the code samples. Some time ago I asked why unit tests use assertions instead of returning a boolean. I didn't get any particularly convincing answers, so I continued returning a boolean, in my home-grown test framework, that's so small it hardly deserves the name 'framework'. One obvious benefit from using exceptions is that you get the name of the test method and class in the exception output. In my framework, I had to explicitly supply that. Each test object had a getName(). return "TestUninstallingDrivers". Ok, now I have duplication:
public static final UnitTest testUninstallingDrivers=
new UnitTest()
{
public boolean test()
{
stuff..
return !card.hasDrivers();
}
public String getName()
{
return "testUninstallingDrivers";
}
};
public static final UnitTest $x=new UnitTest()
{
public boolean test()
{
//Auto-generated method stub. To stop this
//annoying message, go through some dialogs
//that you never really wanted to anyway.
return false;
}
public String getName()
{
return "$x";
}
}
unitTest(testUninstallingDrivers,
{
stuff..;
return !card.hasDrivers();
})
template unitTest(name,body)
{
public static final UnitTest <name>=new UnitTest()
{
public boolean test()
{
<body>
}
public String getName()
{
return "<name>";
}
}
};
