Showing posts with label Mobile testing. Show all posts
Showing posts with label Mobile testing. Show all posts
Tuesday, July 20, 2010
How can smoke testing be applied to mobile testing?
Smoke testing can be done on a Mobile once the latest build has been released to the testing team. Smoke test or build verification is nothing but just the basic functionality check for all the applications, test scope parameters that are involved in mobile application testing, testing very basic and important features of the mobile and also testing the showstopper issues at a higher priority level.
How we test battery back up time using load testing especially for mobile testing ?
Below are given a few scenarios to test the mobile battery backup:
1. Charge the mobile up to maximum capacity.
2. Call to a number and continuously use it until the battery fully drained out. Measure the time of life for one full cycle.
3. Charge the battery up to 20% of it's capacity use it until the battery is fully drained out.
4. Charge the battery up to 40% of it's capacity use it until the battery is fully drained out.
5. Similarly check for 60%,80% of battery charge capacities and measure the battery backup time.
6. Verify the battery life by continuously sending SMSs.
7.Verify the (GUI) power indicating lines or levels correctly displaying or not with respect to actually charged battery level.
8.test the phone in non signal coverage area and measure the battery stand by time. (In non signal coverage area cell continuously searches for signals due to this the power continuously dissipated as radio frequency signals and battery drained very soon)
1. Charge the mobile up to maximum capacity.
2. Call to a number and continuously use it until the battery fully drained out. Measure the time of life for one full cycle.
3. Charge the battery up to 20% of it's capacity use it until the battery is fully drained out.
4. Charge the battery up to 40% of it's capacity use it until the battery is fully drained out.
5. Similarly check for 60%,80% of battery charge capacities and measure the battery backup time.
6. Verify the battery life by continuously sending SMSs.
7.Verify the (GUI) power indicating lines or levels correctly displaying or not with respect to actually charged battery level.
8.test the phone in non signal coverage area and measure the battery stand by time. (In non signal coverage area cell continuously searches for signals due to this the power continuously dissipated as radio frequency signals and battery drained very soon)
What is the advantage of symbian OS devices comparing with j2me and Brew OS devices?
1. Symbian is the latest OS where as j2me and Brew OSs are old ones.
2. Symbian OS has SIS file format where as j2me has JAR file format which means this is a third party software and anybody can develop softwares in this OS.
3. Symbian is a fast browsing and a fast operating system. j2me is not as fast.
4. Symbian OS provide touchscreen phones such as UIQ phones. No such facility on j2me.
5. Symbain OS has superior hardware access to the phone compared to j2me and Brew OS
6. Symbian OS offers rich UI.
2. Symbian OS has SIS file format where as j2me has JAR file format which means this is a third party software and anybody can develop softwares in this OS.
3. Symbian is a fast browsing and a fast operating system. j2me is not as fast.
4. Symbian OS provide touchscreen phones such as UIQ phones. No such facility on j2me.
5. Symbain OS has superior hardware access to the phone compared to j2me and Brew OS
6. Symbian OS offers rich UI.
Subscribe to:
Posts (Atom)