Certified Mobile Software Test Professional (CMSTP)

Objectives of CMSTP

The Mobile Testing Body of Knowledge and the Certified Mobile Software Test Professional has been created to fill a major gap in the skills and knowledge required to effectively test and evaluation of mobile applications and web sites running on mobile devices. The Mobile Testing Certification Taskforce, a special taskforce formed with the IIST Advisory Board, recognized the urgent need for a formal education-based mobile testing certification that is based on a comprehensive body of knowledge to help QA and test professionals meet the challenges of testing mobile devices and applications. The CMSTP is the first education-based mobile testing certification that is based on the comprehensive Mobile Testing Body of Knowledge (MTBOK).

Who Should Pursue the CMSTP

1. All individuals who are responsibile for testing mobile applications or web sites running on mobile devices
2. Test leads and test managers who intend to manage the testing effort for mobile applications
3. Developers interested in conducting more effective testing of mobile applications

Requirements of the CMSTP Pre-requisites:

Before pursuing the CMSTP, Candidates must satisfy one of the following two pre-requisites:

1. Two years experience in software testing. This requirement shall be demonstrated by means of a statement signed by the manager or managers the candidate has worked with.
2. A basic certification in software testing that covers areas 1 and 2 of the Software Test Professionals Body of Knowledge as described by the International Institute for Software Testing. Acceptable certifications are IIST CSTP - Associate Level, ISTQB foundation Level, or CSTE. You may achieve the IIST Certified Software Test Professional - Associate Level either online or at one of our public training events. Click here for details

Formal Education Requirements:

To receive the Certified Mobile Software Test Professional designation, a candidate must complete four days of training covering the 4 areas of the Mobile Testing Body of Knowledge. As approved by the IIST Mobile Testing Taskforce.

CMSTP Training Options Written Exam:

Candidates are required to complete a written exam for each course and pass with a level of performance no less than 80%. For courses conducted by IIST, a candidate is allowed to retake the exam for a second time without having to attend the course again. There is a $100 fee for retakes. If 80% performance is not achieved on a second attempt, the candidate must retake the course or take another course covering the same MTBOK area if available.

Graduation:

Upon satisfying both formal education and job experience requirements, a candidate shall submit an application to the IIST Chairperson for the certification to be granted. Application is available online here. The application must be accompanied by payment of the $180 non- refundable graduation fee. This fee covers the cost associated with record-keeping, grading exams, and certification plaque. Please note there will be an additional $100 for shipping plaques outside the U.S.

CMSTP Re-Certification Requirements

The CMSTP Certification will expire 3 years after it is granted. All CMSTPs must complete the recertification requirements before that time. The re-certification requirements are four days of training to cover any topic in software testing within three years. Days of training may be used to satisfy the requirements of a higher level certification. All training requires attending an exam in each course and achieving 80% performance.

The Mobile Testing Body of Knowledge (MTBOK)

The MTBOK consists of 4 main knowledge areas.  The content of each area is coved by one day of instructor-led training. Like all other Bodies of Knowledge developed by IIST, the MTBOK is a topical Body of Knowledge.  This approach provides instructors the flexibility to cover these topics based on his or her experience. 

Area #1: Mobile Development Technologies

1. Operating Systems:

1. Android, iOS, Windows, etc.
2. Jailbreaking and rooting

2. Hardware: smartphones and tables
3. Types of applications: native apps, mobile websites, hybrid apps
4. Smartphone vendor application distribution process:

1. Apple’s App Store
2. Cydia
3. Android’s Google Play
4. Windows Phone Store
5. Company stores

5. Development technologies and their impact on testing:

1. Web: HTML and HTML5, JavaScript, XML web services, CSS, Web Services 
2. Native apps technologies:
1. Platform-specific languages/technologies, e.g., Objective-C, SWIFT, and Xcode
2. General languages, e.g., Java
3. Multi-platform code generators, e.g., Xamarin and Intel® XDK

Area #2: Mobile Testing Strategies and Techniques

1. Types of Mobile Testing
1. Functionality: how to test location sensitivity, orientation, real-time updates, etc. unique aspects
2. Performance: endurance testing and beyond
1. Device
2. Network
3. Server
4. Interoperability-Interface
3. Compatibility: hardware and software
4. Usability: size, lighting, conditions of use, etc. do matter
5. Security: lost/stolen phones, memory freeze and “Remember Me,” etc.
6. Interoperability: crucial chain in the enterprise link
7. Survivability and Recovery: testing for battery, reception, GPS loss, etc.
8. User acceptance: when, where, and who will do it
9. Production monitoring: what happens after release

2. Mobile Testing Lab

1. Hardware
2. Software
3. Connectivity
4. Security
5. Procedures
6. Build vs. buy: in-house and external test labs

3. Mobile Testing Team

1. The skillset of mobile test engineer
2. Finding mobile testers
3. Training your team

Area #3: Mobile Compatibility Testing

1. Statistics and target user groups
1. Defining your target audience
2. Finding out the prevalent platforms
3. Spotting and extrapolating the trends
4. Real users and user proxies
2. Sensitivity
1. Platform
1. Operating system
2. Browser
3. Hardware
4. Carrier
2. Technology
1. Which parts of your app and website are sensitive to platform-related factors
2. Typical sensitivities and the ways to test them
3. Risk analysis
1. Defining compatibility risks
2. Mapping compatibility risk for your app or website
3. Living with the risk: prioritizing, mitigating, and managing compatibility risks

Area #4: Automated Mobile Testing

1. The necessity to automate
2. Coping with the Mobile Challenges: diverse platforms, weaker hardware, variety of connectivity modes, and interoperability
3. From challenges to criteria for evaluating automation options
4. Different approaches

1. Emulators
2. Hardware modification
3. Software modification: jailbreaking vs. instrumentation
4. Special tools
5. Common tools

5. Choosing the best automation approach
6. Tools for Mobile Testing