CTAL-TA_Syll2019 ISTQB Certified Tester Advanced Level - Test Analyst (Syllabus 2019) Questions and Answers

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)

 System integration testing (SIT) is a type of testing that verifies the interactions and functionality of different components or systems within a larger system. The developers, who are responsible for developing and integrating the components or systems, need to understand the tests to review them for accuracy, completeness, and feasibility. The auditors, who are responsible for ensuring the compliance and quality of the system, need to understand the tests to approve them for execution and reporting. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• System Integration Testing: A Complete Guide2, section “Who Performs System Integration Testing?”
• System Testing vs Integration Testing: Key Differences3, section “What is System Integration Testing?”

The correct answer isA.Functional testing.

Functional testing

Functional testing is the type of testing that focuses on completeness, appropriateness, and correctness characteristics of the application under test. Completeness means that all the functions and features of the application are tested. Appropriateness means that the functions and features are suitable for the intended purpose and meet the user’sneeds.Correctness means that the functions and features produce the expected results and do not contain any errors or defects1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, Section 3.2.2 Functionality
• ISTQB Certified Tester Advanced Level Syllabus Test Analyst3, Section 3.2.2 Functionality
• ISTQB Test Analyst Syllabus and Study Guide4, Section 3.2.2 Functionality

The correct answer isD.Incorporate SUMI to provide objective usability acceptance criteria.

SUMI

SUMI stands for Software Usability Measurement Inventory, which is a questionnaire-based method for measuring user satisfaction with software products, including video games. SUMI can provide objective and reliable feedback on the usability aspects of the product, such as efficiency, effectiveness, learnability, helpfulness, and enjoyment.SUMI can also help to identify the strengths and weaknesses of the product and compare it with other similar products or benchmarks1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Usability
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Usability
• SUMI User Manual4, Section 1.1 What is SUMI?

Exploratory testing is an approach that involves simultaneous learning, test design, and test execution. It is suitable for testing a web application with minimal documentation and tight deadlines. Test chatters are brief notes that describe the test objectives, test ideas, test data, test steps, and test results. They are used to guide the testing and document the test sessions. Test chatters are flexible and adaptable to the changing requirements and feedback from the stakeholders. References = ISTQB Certified Tester Advanced Level Syllabus Test Analyst, Section 2.3.2, Exploratory Testing1; What is Exploratory Testing? - Guru99, Section How to execute Exploratory Tests2

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?

The correct answer isA.Create test data for the keywords that includes error data and verifies the proper error is returned.

Create test data for the keywords that includes error data and verifies the proper error is returned

This is the best way to test the error conditions and still use the keyword-driven tests because it allows the reuse of the existing keywords and functions, while providing different inputs and expected outputs for the test cases.It also ensures that the error checking is automated and consistent, and that the test coverage is adequate1.

References=

• Keyword Driven Testing Framework with Example2, Section How to create Keyword Driven Framework
• What is Keyword Driven Testing: A Detailed Tutorial With Examples3, Section How to perform Keyword Driven Testing
• KEYWORD DRIVEN TESTING4, Section How to do Keyword Driven Testing

The correct answer isD.The story contains more than one item of functionality.

The story contains more than one item of functionality

A user story should be small, simple, and focused on one item of functionality that delivers value to the user. This story combines two items of functionality: querying the balance and withdrawing money. These items could be separated into two different stories, each with its own acceptance criteria and priority.This would make the stories easier to understand, estimate, test, and deliver1.

References=

• User Stories | Examples and Template | Atlassian2, Section User story best practices
• ISTQB Certified Tester Advanced Level Syllabus Test Analyst3, Section 2.1.1 Test Analyst Tasks in the Test Process
• ISTQB Test Analyst Syllabus and Study Guide4, Section 2.1.1 Test Analyst Tasks in the Test Process

State transition testing is a technique that tests the behaviour of a system or component based on its transitions between states in response to events. It is suitable for testing systems that have complex interactions and dependencies, such as a car navigation system that needs to integrate with other car software components. State transition testing can verify the functional correctness of the system by checking if it responds correctly to different inputs and events, and if it reaches the expected states and outputs. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 54, section 4.2.2.2.

The correct answer isC.Conduct pre-test interviews to give instructions to the users, and post-test interviews to get their feedback.

Pre-test and post-test interviews

Pre-test and post-test interviews are methods of usability testing that involve communicating with the business users before and after they test the application. Pre-test interviews can help to explain the purpose and scope of the test, provide instructions and guidance, and establish rapport with the users.Post-test interviews can help to collect feedback, opinions, and suggestions from the users, as well as identify any issues or problems they encountered during the test1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Usability
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Usability
• Usability Testing 101: A Guide for Businesses4, Section 5. How to Conduct a Usability Test

A test design tool is a tool that helps testers create test cases, or at least test inputs, based on the requirements and specifications of the software. It can use various techniques, such as equivalence partitioning, boundary value analysis, decision tables, state transition diagrams, etc., to generate test inputs that cover different aspects of the software functionality and quality. A test design tool does not validate models of the software, execute tests automatically, or trace tests to requirements, although these may be features of other types of testing tools. References = What Is Test Design : Tools and Best Practices; Test Design in Software Testing - A Comprehensive Guide; ISTQB Advanced Level Test Analyst Syllabus 2019, section 3.2.1.

The correct answer isA.It can be used to anonymize production data.

It can be used to anonymize production data

A test data preparation tool is a type of test tool that allows data to be selected from an existing database or created, generated, manipulated and edited for use in tests.One of the capabilities of such a tool is to anonymize production data, which means to mask or replace sensitive or confidential information with fictitious or random data, to protect the privacy and security of the data and comply with the regulations1.

References=

• What is Test data preparation tools in software testing?2
• Top 14 BEST Test Data Management Tools In 20233
• Test Data Preparation Tools: 5 Must-Have Features4

The acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable by the user. They should be defined and testable, meaning that they are clear, measurable, and verifiable. The acceptance criteria for the user story are not well-defined and testable, because they do not specify how the payment is made, how the registration is verified, andhow the monthly limit is enforced. These details are important for testing the functionality and quality of the user story, and should be included in the acceptance criteria. References = ISTQB Certified Tester Advanced Level Syllabus Test Analyst, Section 2.2.1, Use Case Testing1; How to Write a Good User Story, Section Acceptance Criteria2; Test User Stories with these 10 Tests, Section Testable3

Pairwise testing is a technique that reduces the number of test cases by testing only pairs of values for each data item, instead of testing all possible combinations. Pairwise testing is based on the assumption that most defects are caused by interactions of at most two factors. Pairwise testing can be applied to this problem using the classification tree, which shows the data items and their values. By using pairwise testing, the number of test cases will be lower than exhaustive testing, which would require testing every combination of values for each data item. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Data Combination Test (DCoT) | TMap2, section “Coverage level”
• Pairwise Software Testing - GeeksforGeeks3, section “Introduction”

Equivalence partitioning is a technique that divides the input domain into classes of data that are expected to behave similarly. The test sets should cover one value from each equivalence class, as well as the boundary values between them. The equivalence classes for the metro fare system are:

• Before 9:30 am (full fare)
• Between 9:30 am and 5:00 pm (saver ticket)
• Between 5:00 pm and 7:00 pm (full fare)
• After 7:00 pm (saver ticket)

The boundary values are 9:30 am, 5:00 pm, and 7:00 pm. Therefore, the test set that provides the best equivalence partitioning coverage is the one that includes one value from each equivalence class and the boundary values, which is option D. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Boundary Value Analysis and Equivalence Partitioning Testing2, section “Equivalence Partitioning”
• Equivalence Partitioning Method3, section “Example 1: Equivalence and Boundary Value”

Low-level test cases are more suitable for testing software that controls the braking mechanism for commuter trains, as they provide more detail and specificity for verifying the functionality and safety of the system1. Low-level test cases also use predefined data, which is more reliable and consistent than tester-created data, and can be easily traced to the test conditions and requirements2. High-level test cases are more abstract and vague, and may not cover all the possible scenarios and risks involved in testing such a critical system3.

References = 1: Test Case Design: a Guide for QA Engineers With Examples 2: How to Write Test Cases in Software Testing with Examples 3: Test Case vs Test Scenario – Difference Between Them

The requirement states that the system shall allow cash advances of at least 200 Euros, but it does not specify the maximum amount or the conditions for different cards. This could lead to confusion, inconsistency, and errors in the system’s functionality and testing. The requirement should be more precise and define the exact limits and rules for each card type and scenario. References = ISTQBAdvanced Level Test Analyst Syllabus 2019, section 2.1.1; Requirement Analysis Templates & Techniques, section “Requirement Analysis Best Practices”.

Classification trees are a combinatorial testing technique that allows the tester to represent the data items and their values in a graphical form, and to exclude certain combinations by using constraints or rules. Classification trees can help the tester to visualize and organize the test data, and to generate test cases that cover all relevant combinations of values. The other techniques do not provide a convenient way to exclude certain combinations, or require more complex mathematical calculations. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Classification Tree Method for Test Design2, section “Classification Tree Method”
• Classification Tree Method - Tutorialspoint3, section “Classification Tree Method”

Incident logging and reporting is an important part of incident management, as it helps to document the incident details, communicate the incident status, and analyze the incident causes and impacts1. One of the steps in incident logging and reporting is to identify and log any new risks that have surfaced as a result of the incident2. This helps to assess the severity and priority of the incident, as well as to plan for risk mitigation and contingency actions3. Debugging the code and updating the test automation are not part of incident logging and reporting, but rather part of incident resolution and recovery4. None is not a valid answer, as there is always room for improvement in incident management5.

References = 1: 5 Steps to Create an Effective Incident Reporting Procedure 2: 12 Things To Include In An Incident Report Log (Full Guide) 3: Incident reporting procedure example and flow chart 4: What is incident management? Steps, tips, and best practices 5: Incident Management: Process, System, & Tools

A 0-switch test case is a test case that covers one transition from one state to another. To achieve 100% 0-switch coverage, all the transitions in the state diagram must be tested. The state diagram has seven states: Login, Menu, Logout, Withdraw, Deposit, Get Balance, and Access Account. There are 13 transitions in the state diagram, as shown by the arrows. Therefore, 13 0-switch test cases are needed. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• How to Design Test Cases Using State Transition Testing Technique?2, section “0-switch coverage”
• State Transition Testing - Tutorialspoint3, section “State Transition Diagram”

I have searched the web for the ISTQB Advanced Level Test Analyst EXT 2019 documents and study resources, and based on the information I found, I have verified the answer to your question as follows:

Option D

Option D accurately represents the tuition payment rules for both undergraduate and graduate students at Acme University, taking into account the different tuition fees for part-time and full-time students as well as the additional fee for undergraduate students taking more than 18 credit hours. Option D also uses the correct notation for decision tables, such as Y for yes, N for no, and - for don’t care.

References=

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, Section 3.2.2 Decision Tables
• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Decision Tables
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Decision Tables
• ISTQB Certified Tester Advanced Level Overview of Syllabi4, Section 1.3 Content