The plan is to use j2meunit to create automated testing of the application that will run on a mobile handset. There are some challenges with this. Mobile app development is actually quite full of challenges that most of j2ee developers forgot about or mostly don’t care about:
- Memory is very limited.
- Threads
So the main issue with testing is actually about #1, that is that on the target handset the limit size of the jar is 1MB. For the whole project it is quite enough (thanks to proguard for obfuscation). But in order to run tests project can not be obfuscated (try to figure out those stacktraces then), plus the size of the actual test code with the whole j2meunit adds to the size of the jar.
The idea now is to break down the scenarios and create a multiple jars with small set of tests. The outcome is one more challenge: how to deploy it to the handset , run the tests and gather the results. If we are talking about tens of jars right now, and might be hundreds at some point, it can be a real nightmare to manage.
I wonder how other people managed this?
One Comment
Look at this for tracing obfuscated stack prints: http://proguard.sourceforge.net/manual/retrace/examples.html
Post a Comment