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