1. Home
  2. ISTQB
  3. ATTA Exam Syllabus

ISTQB ATTA Exam Syllabus

Start Free ATTA Exam Practice After Reviewing the Topics

Before starting your ATTA exam preparation, it is recommended to review the complete ISTQB Advanced Technical Test Analyst exam syllabus and carefully go through the exam objectives listed below. Once you understand the exam structure and objectives, you should practice using our free ATTA questions. We also provide premium ATTA practice test, fully updated according to the latest exam objectives, to help you accurately assess your preparedness for the actual exam.

ISTQB
Vendor
ATTA
Exam Code
65
Total Questions
28
Total Exam Domains

START FREE ATTA EXAM PRACTICE

NO SIGNUP REQUIRED  •  100% FREE TO START

ATTA EXAM QUESTIONS

ISTQB ATTA Exam Objectives

Section 1: Objective 1:
Weight:
-
  • Summarize the generic risk factors that the Technical Test Analyst typically needs to consider.
Section 2: Objective 2:
Weight:
-
  • Summarize the activities of the Technical Test Analyst within a risk-based approach for testing activities.
Section 3: Objective 3:
Weight:
-
  • Design test cases for a given test object by applying statement testing to achieve a defined level of coverage.
Section 4: Objective 4:
Weight:
-
  • Design test cases for a given test object by applying the Decision test technique to achieve a defined level of coverage.
Section 5: Objective 5:
Weight:
-
  • Design test cases for a given test object by applying the modified condition/decision test technique to achieve full modified condition/decision coverage (MC/DC).
Section 6: Objective 6:
Weight:
-
  • Design test cases for a given test object by applying the multiple condition test technique to achieve a defined level of coverage
Section 7: Objective 7:
Weight:
-
  • Understand the applicability of API testing and the kinds of defects it finds
Section 8: Objective 8:
Weight:
-
  • Select an appropriate white-box test technique according to a given project situation.
Section 9: Objective 9:
Weight:
-
  • Use control flow analysis to detect if code has any control flow anomalies and to measure cyclomatic complexity.
Section 10: Objective 10:
Weight:
-
  • Use data flow analysis to detect if code has any data flow anomalies.
Section 11: Objective 11:
Weight:
-
Section 12: Objective 12:
Weight:
-
  • Apply dynamic analysis to achieve a specified goal.
Section 13: Objective 13:
Weight:
-
  • For a particular scenario, analyze the non-functional requirements and write the respective sections of the test plan.
Section 14: Objective 14:
Weight:
-
  • Given a particular product risk, define the particular non-functional test type(s) which are most appropriate.
Section 15: Objective 15:
Weight:
-
  • Understand and explain the stages in an application’s software development lifecycle where non-functional testing should typically be applied.
Section 16: Objective 16:
Weight:
-
  • For a given scenario, define the types of defects you would expect to find by using the different non-functional test types.
Section 17: Objective 17:
Weight:
-
  • Explain the reasons for including security testing in a test approach.
Section 18: Objective 18:
Weight:
-
  • Explain the principal aspects to be considered in planning and specifying security tests.
Section 19: Objective 19:
Weight:
-
  • Explain the reasons for including reliability testing in a test approach.
Section 20: Objective 20:
Weight:
-
  • Explain the principal aspects to be considered in planning and specifying reliability tests.
Section 21: Objective 21:
Weight:
-
  • Explain the reasons for including performance testing in a test approach.
Section 22: Objective 22:
Weight:
-
  • Explain the principal aspects to be considered in planning and specifying performance testing.
Section 23: Objective 23:
Weight:
-
  • Explain the reasons for including maintainability testing in a test approach.
Section 24: Objective 25:
Weight:
-
  • Explain the reasons for including portability testing in a test approach.
Section 25: Objective 26:
Weight:
-
  • Explain why review preparation is important for the Technical Test Analyst.
Section 26: Objective 28:
Weight:
-
  • Analyze an architectural design and identify problems according to a checklist provided in the syllabus.
Section 27: Objective 29:
Weight:
-
Summarize the activities that the Technical Test Analyst performs when setting up a test automation project.
Section 28: Objective 30:
Weight:
-
  • Summarize the differences between data-driven and keyword-driven automation.
Info
https://istqb.org/wp-content/uploads/2024/11/ISTQB-CTAL-TTA_Syllabus_v4.0.pdf