Quality is delighting customers
Started by Nabanita Sarkar. Last reply by K@!! "U" Dec 9, 2012. 2 Replies 0 Likes
Started by Vadivelan. Last reply by Maheedhar Dec 3, 2012. 1 Reply 0 Likes
Comment
Comment by VJkumran on October 15, 2012 at 4:49pm 1. Weigh the Options — Mobile App or Mobile Website?
“Do you need a mobile application, a mobile website, or both? Before even starting the design process, you need to figure out what format or formats are best suited for your goals. Sometimes this can be really easy. For example, if you want to build a utility or game, you may be better served building a native application rather than worrying about how different mobile browsers will interpret your content.”
2. Consider Where Your App Will Be Used
“Once you’ve decided to make a native mobile app, you’ll want to consider where your application is most likely going to be used. This is important because where and how an application is used can directly impact how it can be designed.
For instance, if you have an application that is going to be used while walking around — a geo-location app or an app that takes advantage of a device’s GPS — making sure that core app functions are easy to see and access is very important.”
3. Be Aware of Various Screen Sizes
“Even on the same mobile platform, screen sizes and resolutions can vary based on device type. For instance, the screen size and resolution on the HTC Incredible is different than that on the HTC EVO 4G. Consequently, for an application to have a consistent look and feel across both devices and across a variety of other devices, user interface elements and graphics need to be scalable.”
4. Follow Existing UI Conventions
“On desktop computers, there are certain user interface elements that make a Windows app a Windows app or a Mac OS X app a Mac app. There are user interface conventions tailored for mobile apps as well. While you don’t have to follow these guidelines 100% of the time, sticking with consistent methods of displaying data and interacting with content will make your app easier to pick up by end-users. Following these conventions will also ensure that your app is consistent with the other applications already on a mobile device.”
5. Design For Touch
“In almost all cases, mobile apps are going to be used while in someone’s hand. Therefore, designing your mobile app around touch and ergonomics is very important.
Think about how you hold your phone in your hand. Now, think about where you thumb sits. That’s why many applications have main menus and selectors at the bottom of the screen and content near the top of the screen. Apps with that type of layout are designed for touch, and yours should be too.”
Comment by Suresh S on October 13, 2012 at 8:54pm Hi All,
If anybody have mobile testing docs to learn, Could you pls share with my id: ssuresh.neni001@gmail.com
Thanks in advance.
Regards,
Suresh
Comment by VJkumran on October 11, 2012 at 1:59pm "How to connect Android phone with computer remotely via teamviewer or crazyremote ?"
Comment by VJkumran on October 3, 2012 at 6:04pm "How to upgrade android firmware from 2.3 to 4.0 for samsung Galaxy Note 7000 using Wi-Fi Connection ?"
Comment by VJkumran on October 3, 2012 at 2:39pm Hi Sreekar,
Find the below mentioned points which is very useful when performing mobile app testing.
1.) Testing mobile applications through
i) Devices.
ii) I phone — Simulator
iii) Android – Emulator
2.) Installation & Uninstallation Testing
3.) Few Security things if the application is a social networking application or links to a social networking applications like facebook, twitter and LinkedIn etc…
4.) Inner functionality — Functional testing
5.) System Crash / Force Close
6.) Performance & Stress Testing
7.) Page scrolling
8.) Navigation to screens
9.) Truncation errors
10.) Data Testing (Contents)
11.) Performance – application and inner pages load time
12.) Network Testing: (if the application is a Network based application)
i) Verify the behavior of application when there is Network problem and user is performing operations for data call.
ii) User should get proper error message like “Network error. Please try after some time”
13.) Application Specific Testing (ie Application behavior Testing based on the Mobile Device used)/ Some Device specific Testing for the Application
14.) Application Side Effects:
i) Make sure that your application is not causing other applications of device to hamper.
ii) Installed application should not cause other applications of device to hamper.
15) Cosmetic issues (look and feel).
Regards,
VJ
Comment by Sree on September 27, 2012 at 9:57am Hi all I am sreekar I am working Mobile Testing can any one tell me the Process in mobile testing
Comment by SANKAR on March 3, 2012 at 4:38pm hi All,
i am sankar i am doing now Manual testing on Online shopping application, now i want to change mobile application testing...
please help me regarding this
This version of the Automation instrument introduces several new features, including:
1) Script editing with a built-in script editor
2) Capturing (recording) user interface actions for use in automation scripts
3) Running a test script from an Xcode project
4) Various API enhancements, including the ability to simulate a device location change and to execute a task from the Automation instrument on the host
5) Running the script from Terminal
Comment by Radhika Raju on November 9, 2011 at 2:47pm Hi all, I am new to mobile app testing. Can anyone share the material on how to do mobile app testing on I-phone, I-pad and Anroid mobiles.
Thank you.
Comment by Malay Parikh on July 21, 2011 at 4:57pm Hi Snehasish
for android testing just go to : www.youwave.com
you can install apk file and access it like android phone.
Director - Head of Global Test Center at Barclays
© 2013 Created by Quality Testing.
You need to be a member of Mobile & iPhone Application Testing to add comments!