Well, unittesting is not the only way to test. Most J2ME/MIDP projects to this day are smaller ones and do not require sophisticated testing and process management. If you need unit testing in J2ME, try out J2MEUnit. I am listed as the maintainer of that project but have not contributed any code for a long time. I can get you hooked up with the current developer if you wish.
The issue of testing in MIDP is not really about unit testing. As Michael says, client applications tend to be very small. The issue with testing is debugging your application on multiple devices. Devices and their behavior vary by carrier and geography, so doing a good QA cycle can be difficult. I believe some companies offer testing services.
Joined: Oct 01, 2001
Sounds painful (read expensive) for small or independent developers. Seems to me the emulators need to allow us to force things like broken connections, etc. So that we don't have to try it live on each type of device coupled with multiple carriers. No wonder I keep hearing that wireless isn't quite "there" yet. But I won't let that stop me...