Difference between revisions of "2016 - Katrina Clokie's Mobile Testing Pathway"
From Vincents CV Wiki
(Created page with "It's a new month and I keen to do [http://katrinatester.blogspot.co.nz/2015/08/mobile-testing-pathway.html Katrina Clokie's Mobile Testing Pathway]") |
m (DirksWikiAdmin moved page Katrina Clokie's Mobile Testing Pathway to 2016 - Katrina Clokie's Mobile Testing Pathway) |
||
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | It's a new month and I keen to do [http://katrinatester.blogspot.co.nz/2015/08/mobile-testing-pathway.html Katrina Clokie's Mobile Testing | + | It's a new month and I keen to do the [http://katrinatester.blogspot.co.nz/2015/08/mobile-testing-pathway.html Mobile Testing Pathway] by Katrina Clokie |
+ | |||
+ | ==Reading the reference list== | ||
+ | ===2010 - Test mobile applications with I SLICED UP FUN! - Jonathan Kohl=== | ||
+ | :[http://www.kohl.ca/articles/ISLICEDUPFUN.pdf link to original pdf] | ||
+ | |||
+ | :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. Also customer feedback) | ||
+ | :*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=== | ||
+ | :[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=== | ||
+ | :[http://karennicolejohnson.com/2012/05/applying-the-sfdpot-heuristic-to-mobile-testing/ link to Karen's blog] [http://www.satisfice.com/articles/sfdpo.shtml link to James Bach's original blog] | ||
+ | |||
+ | :Use the following Mnemonic to generate test ideas for testing almost anything | ||
+ | :*S - Structure (eg system architecture) | ||
+ | :*F - Function (what does it do) | ||
+ | :*D - Data (inputs, outputs, what it processes) | ||
+ | :*P - Platform (What does it depend on) | ||
+ | :*O - Operations (How will it be used) | ||
+ | :*T - Time (how does time affect it) | ||
+ | |||
+ | ===2013 - Mobile testing checklist - Rosie Sherry=== | ||
+ | :[http://www.ministryoftesting.com/wp-content/uploads/2014/01/SmartBear-Mobile-Testing-Checklist-V2.pdf link to pdf], An expanded checklist for mobile test ideas grouped in sections similar to the above mnemonics. | ||
+ | |||
+ | ===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=== |
Latest revision as of 21:58, 21 April 2024
It's a new month and I keen to do the Mobile Testing Pathway by Katrina Clokie
Contents
- 1 Reading the reference list
- 1.1 2010 - Test mobile applications with I SLICED UP FUN! - Jonathan Kohl
- 1.2 2012 - Testing mobile applications with COP (who) FLUNG GUN - Dhanasekar Subramaniam
- 1.3 2012 - Applying SFDPOT to mobile testing - Karen N Johnson
- 1.4 2013 - Mobile testing checklist - Rosie Sherry
- 1.5 2014 - Tips to approach mobile testing - Ministry of Testing & SmartBear Software
- 1.6 2014 - Mobile App Test Coverage Model : LONG FUN CUP - Dhanasekar Subramaniam
- 1.7 2014 - Mobile Testing in a nutshell - Jyothi Rangaiah
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. Also customer feedback)
- 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
- Use the following Mnemonic to generate test ideas for testing almost anything
- S - Structure (eg system architecture)
- F - Function (what does it do)
- D - Data (inputs, outputs, what it processes)
- P - Platform (What does it depend on)
- O - Operations (How will it be used)
- T - Time (how does time affect it)
2013 - Mobile testing checklist - Rosie Sherry
- link to pdf, An expanded checklist for mobile test ideas grouped in sections similar to the above mnemonics.