In classical JUnit you have multiple test methods in a single
class
that match some pattern, test framework iterates through these methods
using relection. CLDC/MIDP does not have reflection API, this is one of
problems that need to be solved when adopting JUnit-like test
frameworks to CLDC/MIDP.
There are not too many solutions to this problem, well
described in Vladimir's
blog. I would...
The very common problem people meet when trying to unit-test
their
MIDlets is that you generally can not do something like this:
public
class MyTest
extends
TestCase {
public
void test() {
MyMIDletApplication myma = new MyMIDletApplication();
assertEquals("Never get here", 7, 8);
...
