When data call request is in active state, the stability of application needs to be tested by removing the battery. This act should not affect the application adversely after restarting the application again.I am just sharing one scenario for a j2me Application which may help you while testing your application.
Scenario: Removed a battery when forground data call was active.
Issue Observed:
- While testing my J2ME application when I came across this scenario, I found that RMS of the application was totally corrupted when application restarted after reinserting the battery. Interestingly user was unable to go beyond the splash screen showing a complete white screen forever.
- This happened when I removed the battery when data call progress status was 50% only and the issue was reproducible 100% of the times.
- Interestingly application was working fine for all other states of data call.
On discussion with the development team, corruption of RMS is natural after playing with the application like that.
Tester’s Perspective:
However a Testing Engineer should make sure that application should gracefully handle this situation by giving some user friendly message, something like, “Unable to launch the application as the database is corrupted. Please delete the application from your phone and reinstall” or so on.(Infact the issue should not come)
Using this experience, I applied same calculations for another application and was successful to replicate the same bug. (This is error guessing which gradually comes and enhances with the experience.)
What is RMS ?
- It is a Record Management Syatem which provides a mechanism through which MIDlets can persistently store data and retrieve it later.
