2016 - Katrina Clokie's Mobile Testing Pathway: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
:*I - Inputs (keyboard/touch/peripherals) | :*I - Inputs (keyboard/touch/peripherals) | ||
:*S - Store (good source for product claims & marketing material) | :*S - Store (good source for product claims & marketing material) | ||
:*L - Location (where you are matters, G3, G4, WiFi, moving between) | :*L - Location (where you are matters, G3, G4, WiFi, moving between, turn location service off) | ||
:*I - Interactions/Interruptions (from other applications running on the resource limited mobile) | :*I - Interactions/Interruptions (from other applications running on the resource limited mobile) | ||
:*C - Communication (can you still make/receive calls/txt's/emails) | :*C - Communication (can you still make/receive calls/txt's/emails) | ||
| Line 19: | Line 19: | ||
:*N - Network (mobile connectivity is a multitude of unreliability) | :*N - Network (mobile connectivity is a multitude of unreliability) | ||
===2012 - Testing mobile applications with COP (who) FLUNG GUN - Dhanasekar Subramaniam=== | |||
:[http://moolya.com/testing-stories/test-mobile-applications-with-cop-who-flung-gun/ link to original blog] | |||
:Use the following Mnemonic to generate test ideas for mobile app testing (many are repeats from above) | |||
:*C - Communication | |||
:*O - Orientation (of the device) | |||
:*P - Platform | |||
:*F - Function | |||
:*L - Location | |||
:*U - User Scenarios | |||
:*N - Network | |||
:*G - Gestures (swipe, multitouch, shake, pich etc) | |||
:*G - Guidelines (from Apple/Android etc) | |||
:*U - Updates (& downgrades) | |||
:*N - Notifications (banner, alerts, when locked, push) | |||
*2012 - Applying SFDPOT to mobile testing - Karen N Johnson | *2012 - Applying SFDPOT to mobile testing - Karen N Johnson | ||
*2013 - Mobile testing checklist - Rosie Sherry | *2013 - Mobile testing checklist - Rosie Sherry | ||
Revision as of 00:02, 1 December 2016
It's a new month and I keen to do the Mobile Testing Pathway by Katrina Clokie
Reading the reference list
2010 - Test mobile applications with I SLICED UP FUN! - Jonathan Kohl
- Use the following Mnemonic to generate test ideas for mobile app testing
- I - Inputs (keyboard/touch/peripherals)
- S - Store (good source for product claims & marketing material)
- L - Location (where you are matters, G3, G4, WiFi, moving between, turn location service off)
- I - Interactions/Interruptions (from other applications running on the resource limited mobile)
- C - Communication (can you still make/receive calls/txt's/emails)
- E - Ergonomics (consider overuse issues of suboptimal ergonomics)
- D - Data (follow the data, scope the breath of data)
- U - Usability (follow the emotions, do people like using the app)
- P - Platform (consider the hardware eg hi/lo specs, and the OS and ecosystem)
- F - Function (does it do what it should)
- U - User Scenarios (go on a real user's journey through the app)
- N - Network (mobile connectivity is a multitude of unreliability)
2012 - Testing mobile applications with COP (who) FLUNG GUN - Dhanasekar Subramaniam
- Use the following Mnemonic to generate test ideas for mobile app testing (many are repeats from above)
- C - Communication
- O - Orientation (of the device)
- P - Platform
- F - Function
- L - Location
- U - User Scenarios
- N - Network
- G - Gestures (swipe, multitouch, shake, pich etc)
- G - Guidelines (from Apple/Android etc)
- U - Updates (& downgrades)
- N - Notifications (banner, alerts, when locked, push)
- 2012 - Applying SFDPOT to mobile testing - Karen N Johnson
- 2013 - Mobile testing checklist - Rosie Sherry
- 2014 - Tips to approach mobile testing - Ministry of Testing & SmartBear Software
- 2014 - Mobile App Test Coverage Model : LONG FUN CUP - Dhanasekar Subramaniam
- 2014 - Mobile Testing in a nutshell - Jyothi Rangaiah