1 / 28

ASTQB Mobile Tester Certification

The growing need for mobile testers who know about mobile testing has led to the development of the ASTQB Mobile Tester Foundation Level certification. This certification allows us to control the content and quality of the exam, and work with training providers to develop materials. Join the ASTQB and become a certified mobile tester today!

markortiz
Download Presentation

ASTQB Mobile Tester Certification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ASTQB Mobile Tester Certification Now available!

  2. Market Need Identified • Requests were received from our certification holders • 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

  3. 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

  4. ASTQB Certification • Multiple types of certifications out in the world • 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

  5. Syllabus Development Process • Working group selected (chair and workers) • Syllabus is developed • Internal reviews are conducted and comments incorporated • External reviews are conducted and comments incorporated • Syllabus is ready!

  6. 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

  7. 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

  8. Business Objectives • MOB1 – Identify and mitigate the challenges that face a mobile application tester. • MOB2 – Plan, design and implement appropriate test cases for mobile applications. • 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 applications. • 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.

  9. 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 tasks). • 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.

  10. Syllabus Structure 845 mins = 14 hours

  11. Chapter 1 Introduction – 75 mins

  12. 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 applications • 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 applications

  13. Chapter 2 – Test Planning and Design

  14. Chapter 2 LOs • MOB-2.1.1 (K2) Explain why use cases are a good source of testing requirements for mobile applications • 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 conducted • MOB-2.5.1 (K2) Describe how test analysts should take the device and application into consideration when creating test conditions

  15. Chapter 3 – Quality Characteristics

  16. Chapter 3 - continued

  17. 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

  18. 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

  19. Chapter 4 – Environments and Tools

  20. Chapter 4 – Environments and Tools

  21. Chapter 4 – Environments and Tools

  22. Chapter 5 – Future-Proofing

  23. 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 mindmapsemulator in glossary • Native device - The actual physical device that is running a mobile application

  24. 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 soon

  25. Where to take the exam?

  26. Next Steps • Already an interest in an Advanced Level syllabus • 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

  27. ASTQB Site • 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: www.astqb.org

More Related