What is RMS, Testing For Data
Calls in J2ME Mobile Application
When request for Data Call is under the
Active State, the stability of applications requires to be test by
the battery removing. Such act shouldn't effect the app adversely
after the re-starting the app again. We are just sharing one
scenarios for the J2me applications which can help us during the our
application testing.
Scenarios: When for-ground data
call was active the battery require to remove.
Observed Issues: - During our
J2ME applications testing when we come across from such scenarios, We
found that RMS of the applications was corrupted totally so when app
re-started after the battery reinserting. Users who were interested
but unable to move beyond the screen of splash displaying a complete
screen with in white color forever.
- These took place when we moved the battery when there is 50% progress in status of data call and the 100 time issue is reproducible.
- Interested Applications were working fine for the all another state of the data calls.
While Discussions with the developers
team, corruptions of RMS is the natural after application playing
like it.
Perspective of Tester:
Moreover the Testers should confirm
that the applications should be handle gracefully with this
situations by providing some messages of user friendly, for an
example like - “Unable to Launch the application due to
corrupted database. Please delete the app from this phone and
re-install it- thanks' and so
on. In-fact the bug shouldn't generate.
With
this Experience, We applied same calculation for the other app and
was successful to replicates the same bugs. This is the bug assuming
which gradually come and the enhance with the experiences.
What is RMS
Or the Definitions of RMS?
- RMS stands for Record Management System which gives a mechanism through which MIDlets can persistently save record and later on the requirement can be retrieve it.
What is RMS |
About
RMS and its full definitions we can read on following URL-
http://www.ibm.com/developerworks/library/wi-rms/
No comments:
Post a Comment