iSQI CTAL-TA_Syll2019 Dumps

The correct answer isD.Traceability documentation.

Traceability documentation

Traceability documentation is a way of linking the requirements and use cases to the test cases, test results, and other artifacts that are related to them. It helps to ensure the completeness, consistency, and coverage of the testing process, as well as to facilitate the impact analysis, change management, and defect tracking.Traceability documentation should be added to the checklist for the requirements/use case review, as it is an important part of the test analyst’s role and responsibilities1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 2.1.1 Test Analyst Tasks in the Test Process
• ISTQB Test Analyst Syllabus and Study Guide3, Section 2.1.1 Test Analyst Tasks in the Test Process
• Requirements Traceability Matrix (RTM) - A Complete Guide4, Section 1. What is Requirements Traceability Matrix?

In a keyword-driven test automation approach, the Test Analyst is responsible for defining the keywords that represent the actions and expected outcomes of the test cases. The keywords are then implemented by a developer or a tool as reusable functions or scripts that can be executed by the test automation framework. For example, the Test Analyst can define keywords such as “transfer”, “check balance”, “verify balance”, etc. for the account transfer user story. These keywords can then be used to design test cases in a data-driven or table-driven format, such as:

Table

Keyword

Parameter 1

Parameter 2

Parameter 3

transfer

Lars

Ann

150

check balance

Ann

-

150

verify balance

Ann

-

150

transfer

Tim

Ann

300

check balance

Ann

-

450

verify balance

Ann

-

450

References = Keyword Driven Testing Framework with Example (Section 1 and 2), What is Keyword Driven Testing: A Detailed Tutorial With Examples (Section 1 and 2), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 4.2.1 and 4.2.2)

The level of detail and documentation required for test cases in the project depends on the type of application under test, the standards followed by the organization, and the maturity of the development process. For a web application that is undergoing frequent changes, it is advisable to use high-level test cases that describe the main features and functionalities from a user’s perspective, and low-level test cases that provide more details and specifications for each feature. High-level test cases can be supported by low-level test cases to ensure traceability between the requirements and the test scenarios, as well as to facilitate future changes or enhancements. Low-level test casescan also be reviewed and updated by the end-users who have extensive domain knowledge and are involved in the project. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Test Documentation in Software Testing (Example)3, section “Best practice to Achieve Test Documentation”