recently i got a app on palm to test. can anyone say about the process they follow in testing the palm app.
-i have the emulator and ROM files to test(for testing in diff OS and HW)
-i have tested the app interface, functionality
what else to be tested and what tools needed to be tested :
I would strongly suggest you get the actual devices if you can. Testing on the emulator is great for finding bugs in the early stages, but it doesn't assure the quality of the end product. If you look through other threads in this topic, you will see that there are some limitations when testing with just the emulator.
As far as what else to test, well, that depends
I've tested desktop, iPAQ, web-based and PDA apps and found the same basic concepts exist for all. Try to think of ways you can stress the app - obviously you can't have different apps running in the background but there should be other ways to stress it once you start thinking about it. You may also want to think about Palm architecture. A simple test that comes to mind is associating the app with any of the buttons and ensuring the app launches. Go through the Prefs and see if any of those will interact with your product.
Basically, what you want to do is understand how the Palm works, get to know the subtle differences between each OS and how that could compromise the functionality of your app. I find the more you know about the system being used, the more defects you can find. Would also suggest you purchase or borrow a book for Palm power-users (we have "How to Do Everything with Your Palm"). May give you an idea how a user would use the Palm and your app on the Palm.
I agree with Gsh on this one. It's extremely important to test on the actual device. I've run into numerous memory issues that were only found on the device.
My recommendation would be to use the emulator to sanity check or automate testing on the backend. Also, when you do encounter a bug on the device I recommend you try to regress it on an emulator. If the bug appears on the emulator, it is much easier for developers to track the problem down and regress it.
Lastly, there are a couple of Palm OS applications that may help your team nail down bugs for dev. One tool that we use a lot is called DebugPrefs. It's an application that is used to trap errors that crash the device. Basically, instead of a crash, the device will freeze. Once in this state, you can pull a stack trace from the device and give that to dev along with the bug report. In my experience, this makes bug resolution much faster.
recently i got a application which is Palm OS based and developed with AppForge.This application is connected with java server.users login thru the emulator and the requests go to the server.so i have to test the load of the users logging into the device.i have tried loadrunner for this but it is not accepting as this is not an exe file (this is .prc file)so i request anybody to give me the suggestion whether any tool available for testing these type of app.if not have any suggestins plz give me in testing the palm app.
if possible send me a mail firstname.lastname@example.org
I don't know about other toolsets but with the Rational toolset it is always possible to test as there is the TSS framework which will basically let you write your own test scripts and then run them from within TestManager.