the Mobile Syllabus Announcement PPT

ASTQB Mobile Tester
Now available!
Market Need Identified
• Requests were received from our certification
• Growing need for mobile testers who know
about mobile testing
– Mobile world is expanding
– Traditional apps now have mobile presence
• Even if you’re not a mobile tester, you are
probably a mobile user
Why an ASTQB Syllabus?
• The market has a need for a Mobile Tester
Foundation Level syllabus and certification
• The ASTQB has developed this certification
– Allows us to control the content
– Allows us to control the quality of the exam
– Allows us to work with many training providers as
they develop their materials
– Builds on the knowledge from the Foundation
Level certification
ASTQB Certification
• Multiple types of certifications out in the
• The new syllabus is added to our existing
ISTQB and IQBBA offerings
• The ASTQB has a strong reputation for quality
and experience with creating syllabi
• The new syllabus is ASTQB-developed and
reviewed by an international community
Syllabus Development Process
• Working group selected (chair and workers)
• Syllabus is developed
• Internal reviews are conducted and comments
• External reviews are conducted and
comments incorporated
• Syllabus is ready!
ASTQB Syllabus Experience
ISTQB Foundation – Authors
ISTQB ATA – Chair, authors
ISTQB ATTA – Authors
ISTQB ATM – Chair, authors
ISTQB Expert TM – Chair, authors
ISTQB Advanced Test Automation – Chair, authors
ISTQB Advanced Security – Chair, authors
IQBBA – Contributing editor
ISTQB Adoption
ISTQB may choose to adopt this syllabus
Decision won’t be made until March 2016
Present offering will be worldwide
Syllabus already conforms to ISTQB standards
Business Objectives
MOB1 – Identify and mitigate the challenges that face a mobile application tester.
MOB2 – Plan, design and implement appropriate test cases for mobile
MOB3 – Work with other team members to identify and assess risks and to
implement a testing solution to help mitigate those risks.
MOB4 – Identify the applicable quality characteristics for a mobile application and
identify an appropriate testing approach to address those characteristics.
MOB5 – Participate in tool analysis and selection to select the most appropriate
tools for conducting mobile application testing.
MOB6 – Identify areas for non-functional testing and prepare appropriate tests for
those areas.
MOB7 – Understand the differences between the various mobile application types
and select appropriate tools, techniques and approaches to test those
MOB8 – Effectively employ simulators, emulators and the cloud for testing.
MOB9 – Participate in planning for the future, including proper tool selection and
building for maintainability.
Learning Objectives
– Level 1: Remember (K1)
• The candidate will recognize, remember and recall a term or concept.
– Level 2: Understand (K2)
• The candidate can select the reasons or explanations for statements related to the
topic, and can summarize, differentiate, classify and give examples for facts (e.g.,
compare terms), the testing concepts, test procedures (explaining the sequence of
– Level 3: Apply (K3)
• The candidate can select the correct application of a concept or technique and apply it to
a given context. K3 is normally applicable to procedural knowledge. There is no creative
act involved like evaluating a software application, or creating a model for a given
software program. When we have a given model and cover in the syllabus the procedural
steps to create test cases from a model, then it is K3.
– Level 4: Analyze (K4)
• The candidate can separate information related to a procedure or technique into its
constituent parts for better understanding, and can distinguish between facts and
inferences. Typical application is to analyze a document, software, project situation and
propose appropriate actions to solve a problem or task.
Syllabus Structure
Chapter 1: Introduction to Mobile Testing – 75 mins
Chapter 2: Test Planning and Design – 60 mins
Chapter 3: Quality Characteristics for Mobile Testing – 290
Chapter 4: Environment and Tools – 285 mins
Chapter 5: Future-Proofing – 135 mins
845 mins = 14 hours
Chapter 1 Introduction – 75 mins
What is a Mobile Application
Expectations from Mobile Users
Challenges for Testers
• Frequent Releases
• Portability/Compatibility
Necessary Skills
Equipment Requirements
Lifecycle Models
Chapter 1 LOs
• MOB-1.2.1 (K2) Explain the expectations for a mobile
application user and how this affects test prioritization
• MOB-1.3.1 (K2) Explain the challenges testers encounter in
mobile application testing and how the environments and
skills must change to address those challenges
• MOB-1.3.2 (K2) Summarize the different types of mobile
• MOB-1.5.1 (K2) Explain how equivalence partitioning can
be used to select devices for testing
• MOB-1.6.1 (K2) Describe how some software development
lifecycle models are more appropriate for mobile
Chapter 2 – Test Planning and Design
Identify Functions and Attributes
Identify and Assess Risks
Determine Coverage Goals
Determine Test Approach
Identify Test Conditions and Set Scope
Regression Testing
Chapter 2 LOs
• MOB-2.1.1 (K2) Explain why use cases are a good
source of testing requirements for mobile
• MOB-2.2.1 (K2) Describe different approaches to
risk analysis
• MOB-2.3.1 (K2) Explain how coverage goals will
influence the level and type of testing to be
• MOB-2.5.1 (K2) Describe how test analysts
should take the device and application into
consideration when creating test conditions
Chapter 3 – Quality Characteristics
Functional Testing
Test Design
Chapter 3 - continued
Non-Functional Testing
Performance Testing
Usability Testing
Portability Testing
Reliability Testing
Chapter 3 – Functional LOs
• MOB-3.2.1 (K3) For a given mobile testing project apply
the appropriate test design techniques
• MOB-3.2.2 (K1) Recall the purpose of testing for the
correctness of an application
• MOB-3.2.3 (K2) Explain the important considerations for
planning security testing for a mobile application
• MOB-3.2.4 (K2) Summarize the concepts of perspectives
and personas for use in mobile application testing
• MOB-3.2.5 (K2) Summarize how device differences may
affect testing
• MOB-3.2.6 (K2) Explain the use of Teststorming for
deriving test conditions
Chapter 3 – Non-Functional LOs
• MOB-3.3.1 (K3) Create a test approach that would
achieve stated performance testing goals
• MOB-3.3.2 (K1) Recall aspects of the application that
should be tested during performance testing
• MOB-3.3.3 (K2) Explain why real devices are needed
when simulators are used for testing
• MOB-3.3.4 (K3) For a given mobile testing project,
select the appropriate criteria to be verified with
usability testing
• MOB-3.3.5 (K2) Explain the challenges for portability
and reliability testing mobile applications
Chapter 4 – Environments and Tools
• Application to Mobile
• Generic Tools
• Commercial or Open Source Tools
Environments and Protocols
• Environment Considerations
• Protocols
Chapter 4 – Environments and Tools
Specific Application-Based Environment Considerations
• Browser-based Applications
• Native Device Applications
• Hybrid Applications
Real Devices, Simulators, Emulators and the Cloud
• Real Devices
• Simulators
• Emulators
• Cloud
Chapter 4 – Environments and Tools
Performance Test Tools and Support
Test Automation
• Tool Support
• Skills Needed
Chapter 5 – Future-Proofing
Expect Rapid Growth
Build for Change
• Architect the Testing
• Enable Efficient Maintenance
• Select Tools for Flexibility
• Select Partners Carefully
Plan for the Future
• Lifecycle Models
• Alternative Testing
Anticipating the Future
New Terms
Hybrid application - A mobile application that requires communication with the
web server but also utilizes plug-ins to access device functionality
Mobile application testing - Testing that is conducted on mobile applications
Mobile web application - A mobile application that is designed for use by a variety
of devices with the majority of the code residing on the web server
Native mobile application - A mobile application that is designed for a specific
device family and is coded to access specific functionality of the device normally
via tools that have been specifically designed for the device.
Mobile application - A general term for a software application that is used via a
mobile device such as a smart phone
Minimal essential test strategy - A lightweight approach to risk analysis sometimes
used when testing mobile applications
Geolocation - The identification of the real-world geographical location of a device
Teststorming - A technique used to derive test cases using techniques such as
brainstorming or mindmaps emulator in glossary
Native device - The actual physical device that is running a mobile application
How Does This Work?
• Training is not required, but will be offered
• Self-study from the syllabus and publications
is possible
• E-learning and courses will likely be available
1 hour
Where to take the exam?
After an onsite course
From a Kryterion testing center
At a public location – such as a STAR conference
Next Steps
• Already an interest in an Advanced Level
• Foundation is for those starting out (willingly
or unwillingly!)
• Advanced will have more on environments,
tools, and techniques specific to mobile
• Timeframe not known yet
• Considering adding a practical component
• We will be adding more content, including:
– Download link for Syllabus
– Download link for sample exam
– Feedback link
– Exam registration link
– For now, your key link is: