Sunday, April 20, 2008

Testing J2ME applications

Some tips about testing your J2ME mobile application

if you plan to sign your application:
  1. most probably there will be problem with various vendors and operators (because there is no standard what root certificates must be installed on phones). Be sure to check if it is possible to install your application of target phones and markets.
  2. If there is no specific reason why to sign application, leave it unsigned. You will save money and time for testing.
If your application will use network:
  1. check how application behaves on different networks, as there could be differences (time out settings, port restrictions etc). Especially if you use socket connections.
  2. Analyze data usage of your application (Http connections will typically use more data than socket connections)
  3. Check how your connection behaves on various phone events (calls, suspended application, phone "sleep" mode, calendar events, network loss, etc)
If your application will store data on memory:
  1. check if you don't store sensitive user data.
  2. If you need to store sensitive user data, check that they are encrypted.
  3. Use oxygen phone manager to extract RMS data. For some phones (like Nokia N95) you can view RMS data by viewing hidden memory card contents via PC.

4 comments:

Christine Lemke said...

Your posts are all very relevant and helpful. So thanks. We're currently looking at pros and cons of outsource mobile app QA. Any thoughts? It's been incredibly difficult to find a vendor...

Mobile QA said...

Hi, yes sure, I can share my experience - can you leave your contacts? or send email to me - mobilej2meqa@gmail.com. I have been working on analyzing pros/cons for outsourcing QA.

臭屁毛 said...

hi.i have a issue about RMS.can RMS specify where i want to store in the handset? just like exernal memory card.

vipin said...

excellent stuff
http://soft-engineering.blogspot.com