CP-M-MAT
What is CP-M-MAT?
CP-M-MAT stands for “Certified Professional – Mobile – Master Agile Testing”.
CP-M-MAT can be taken by anyone who wants to become a master of mobile agile testing. The only pre-requisite is that the person should be familiar with using smart phones and have exposure to various kind of smart phone applications.
The course is applicable for all roles and not just “testers”. Knowledge, experience & certification is consciously designed to focus on “agile testing” and not on “agile testers”.
How is it useful?
CP-M-MAT prepares you for testing smart phones native apps, web apps and hybrid apps. Mobility and wearables around mobile technology is the fastest growing application area and there is a dearth of software testing professionals capable of testing mobile apps. The standard software testing approach may not work for mobile areas. This course helps in understanding and utilizing a comprehensive mobile testing strategy using real devices and emulators/simulators for android and iOS.
The course introduces the participant to agile concepts and takes them through multiple sprints (iterations), exposing them to master the art of mobile testing with hands on exercises using agile tool kit implementation for KANBAN boards and retrospectives.
Participants will also get access to a mind-map based mobile testing strategy tool kit and ready to use checklist around various strategy areas.
The course introduces the participants through various facets of mobile testing strategy called as “GUIDABLE INCLUSIONS”
- G Gesture
- U User Stories & Usability
- I Integration
- D Device & Platform
- A Accessibility
- B Browser
- L Location
- E Efficiency
- I Interrupts
- N Notification
- C Conformance
- L Localization
- U Updates
- S Synchronization
- I Interactions
- O Orientation
- N Network
- S Security
Am I Eligible?
Everyone who wants to master mobile application testing is eligible for this course. There is no pre-requisite for this course except for the following:
- Participant should have used smart phones and is having a smart phone to use for practical testing during the program.
- Participant should understand basic smart phone terminologies like APK, Android, iOS, Emulator, Device, Browser, market place, play store.
- Participant should understand basic software development and testing terminology e.g. SDLC, STLC, Waterfall and other Software development models, Testing, Test Execution, Test Planning, Test Preparation, Defect, Test Case Pass / Fail, Requirement.
- Participant should have worked on MS-Office or similar products to MS Excel, MS Word.
- Participants should be comfortable installing new applications and software on desktops and mobile.
- Please go through the eligibility exams on the ATA website to judge your knowledge and understanding on the points mentioned above.
- If you need help in finding out reference material to understand the terminology mentioned, please get in touch with ATA: atasupport@agiletestingalliance.org
Duration
CP-M-MAT is designed specifically for corporates and working professionals alike. If you are a corporate you can opt for either 5 half days course or 3 days course followed by an examination. If you are a working professional opt for 3 days course followed by an examination.
-
1. Introduction to Agile and relevance to mobile application development
- 1.1. Agile in Action – using Penny Game exercise
-
1.2. Introduction to Scrum
- Roles
- Artifacts
- Ceremonies
- Overall Agile Process flow
-
1.3. Introduction to KANBAN
- Value Stream Map
- Work In Progress Limits
- KANBAN with SCRUM
- Overall Agile Process flow
-
1.4. Introduction to Mobile Applications
- Need and growing importance of Mobile Testing
- Mobile Testing challenges
- Understanding Native Apps V/s Web Apps V/s Hybrid Apps
- Understanding the need for testing on various Devices and Platforms
- Exercise on installing emulators for Android and iOS
-
1.5. Introduction to Exploratory Testing
- Using Session sheet to test Apps
- Exercise on Exploratory Testing
-
2. Mobile Application Testing Strategy – GUIDABLE INCLUSIONS
-
2.1. G – Gesture
- Understanding various Gestures for Mobile Application
- Touch events
- Drag and drop
- Multi-touch actions
- Longpress, Pinching, expanding actions and many more
- Testing Getures
- Examples
- Case Study and exercises
-
2.2. U – User Stories & Usability
- Understanding User Scenarios and Usability for Mobile Applications
- Testing various different user types and workflows that define the purpose of the applications
- Testing usability aspects for the workflows and their testing
- Examples
- Case Study and exercises
-
2.3. I – Integration
- Understanding User Integration aspects for Mobile Applications across API’s, within the device and many other integration aspects that govern the behavior of the mobile application
- Testing various different user types and workflows that define the purpose of the applications
- Testing usability aspects for the workflows and their testing
- Examples
- Case Study and exercises
-
2.4. D – Device & Platform
- Understanding User Integration aspects for Mobile Applications across API’s, within the device and many other integration aspects that govern the behavior of the mobile application
- Testing various different user types and workflows that define the purpose of the applications
- Testing usability aspects for the workflows and their testin
- Examples
- Case Study and exercises
-
2.5. A – Accessibility
- Understanding Accessibility aspects for Mobile Applications
- Testing Accessibility for mobile
- Examples
- Case Study and exercises
-
2.6. B – Browser
- Understanding the importance of multiple browser testing for web apps and hybrid apps and their interactions with the native apps if any
- Testing web apps using browser
- Examples
- Case Study and exercises
-
2.7. L – Location
- Understanding Locations aspects like – GPS and its impact if any for Mobile Applications
- Testing Location specific aspects for mobile
- Examples
- Case Study and exercises
-
2.8. E – Efficiency
- Understanding efficiency/performance aspects for Mobile Applications – like usage of CPU, Memory and other resources
- Testing performance and efficiency for mobile apps
- Using third party tools for measuring efficiency/performance parameters
- Competitor performance benchmarking
- Examples
- Case Study and exercises
-
2.9. I – Interrupts
- Understanding the impacts of interrupts like voice calls and messages etc while the app is running
- Testing app behavior under the influence of various interupts for mobile
- Examples
- Case Study and exercises
-
2.10. N – Notification
- Understanding different and possible notifications
- Testing the read and unread notifications and actions on those notifications for mobile apps
- Examples
- Case Study and exercises
-
2.11. C – Conformance
- Understanding various conformance parameters for making the application available on the different market places
- Android market place conformance guidelines
- iOS market place conformance guidelines
- Windows mobile market place guidelines
-
2.12. L – Localization
- Understanding impact of languages and their usability aspects for Mobile Applications
- Testing simple localization areas for mobile
- Examples
- Case Study and exercises
-
2.13. U – Updates
- Understanding how mobile apps updates, OS level updates can impact the existing user base
- Testing to reduce the risk associates with updates and ensuring updates happen seamlessly
- Examples
- Case Study and exercises
-
2.14. S – Synchronization
- Understanding that the mobile apps can be accessed across different and multiple devices at any given time, the need to synchronize the data across various platforms and devices and test the same
- Examples
- Case Study and exercises
-
2.15. I – Interactions
- Understanding interactions including starting the app, shutting down the application, performing various actions on the applications using the user interface
- Testing various interactions for mobile apps
- Examples
- Case Study and exercises
-
2.16. O – Orientation
- Understanding the mobile application behavior when the orientation changes from landscape to portrait mode. Various other orientation related aspects and testing the same
- Examples
- Case Study and exercises
-
2.17. N – Network
- Understanding network related aspects that can impact the reliability and availability of the mobile app
- Testing resilience and availability due to network issues
- Examples
- Case Study and exercises
-
2.18. S – Security
- Understanding the importance of securing the data across various devices
- Testing security aspects for mobile
- Examples
- Case Study and exercises
-
2.1. G – Gesture
-
3. Mobile Testing strategy – GUIDABLE INCLUSIONS application in real mobile app sprints
-
3.1. Agile Practical – Sprint 1
- Plan, prepare and execute “GUIDABLE INCLUSION” for a real app for the first sprint
- How to use android simulators
- Configuring mobile devices for APK testing
- Executing the mobile testing strategy on real devices and emulators/simulators
- Identifying defects
- Report defects in the agile environment for the mobile app
- Taskboards
- Retrospectives
-
3.2. Agile Practical – Sprint 2
- Plan, prepare and execute “GUIDABLE INCLUSION” for a real app for the first sprint
- How to use android simulators
- Configuring mobile devices for APK testing
- Executing the mobile testing strategy on real devices and emulators/simulators
- Identifying defects
- Retesting and regression testing
- Report defects in the agile environment for the mobile app
- Taskboards
- Retrospectives
-
3.1. Agile Practical – Sprint 1
-
4. Introduction for need for Automation in Mobile Applications
- Introduction to available automation tools for mobile
- Need and importance for using automation
- Introduction to CP-M-AAT
