iSQI CTAL-TA_Syll2019 ISTQB Certified Tester Advanced Level - Test Analyst (Syllabus 2019) Exam Practice Test

A decision table is collapsed when duplicate or impossible cases are removed. In this decision table, there are two duplicate cases: column 2 and column 4 have the same actions (A1 and A2), and column 5 and column 6 have the same action (A1). There are also two impossible cases: column 7 and column 8 have no actions, which means that there is no outcome for these combinations of conditions. Therefore, after collapsing the decision table, only two cases are left: column 1 and column 3, which have different actions (A1 and A2 for column 1, and A1 for column 3). References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Decision Table-Based Testing2, section “Don’t Care Entries and Rule Counts”
• A Guide on Building Decision Tables3, section “How to ensure that the Table is Complete?”

Defect taxonomies are categorized lists of defects that can be used to identify and prevent common types of errors in software development and testing. They can also be used to design test cases that target specific defect types, such as security vulnerabilities. Therefore, using a list of known defect types to penetrate the security of computer systems is an example of the use of defect taxonomies. References = Defect Taxonomies - The Practical Guide to Defect Prevention (Chapter 10), Using Defect Taxonomies for Testing Requirements, Defect Based Approach using Defect Taxonomy, Requirements-based testing with defect taxonomies

State transition is a technique that analyzes the behavior of an application for different input conditions and how it changes from one state to another in response to events. It is useful for testing scenarios where the date of reservation is a critical factor that affects the system state and output1

References =

• ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.2.3, page 432
• State Transition Testing – Diagram & Technique (Example) - Guru993
• State Transition Testing - GeeksforGeeks4

A Test Analyst is responsible for testing the functional and non-functional aspects of the system that are related to the business domain, user needs, and quality characteristics. A Test Analyst will typically test the requirements that specify the expected behavior and functionality of the system, such as P101, P102, and P103. P104 is a performance requirement that specifies a measurable criterion for the system’s efficiency and responsiveness. This type of requirement is usually tested by a Technical Test Analyst, who has the skills and tools to design and execute performance tests. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst 2019, Chapter 1.1.2, Roles and Responsibilities of the Technical Test Analyst; ISTQB Certified Tester Advanced Level Syllabus Test Analyst 2019, Chapter 1.1.2, Roles and Responsibilities of the Test Analyst; ISTQB Glossary, Version 4.0.2, Performance Testing, Functional Testing, Non-functional Testing.

Experience-based testing is a technique that relies on the tester’s intuition, skills, and past experiences to create test scenarios. However, this approach makes it challenging to measure and assess the test coverage, as there is no clear criteria or method to determine which areas of the software have been tested and which have not. This can lead to gaps in the testing process and potential risks of missing defects1

References =

• ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.3.1, page 462
• Experience Based Testing: What It Is and Why It Matters?3
• Experience based testing technique - ToolsQA4

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

Boundary value analysis is a technique that focuses on testing the values at the boundaries of valid and invalid partitions. It is suitable for testing the errors caused by incorrect use of relational operators in the code, such as “>” and “<” instead of “>=” and“<=”. By creating test cases using boundary value analysis, the tester can verify that the system handles the borderline cases correctly and does not miss any edge cases.

References =

• ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.2.2, page 411
• Software Testing - Boundary Value Analysis - GeeksforGeeks2
• State Transition Testing – Diagram & Technique (Example) - Guru993

Pairwise testing is a technique that tests all possible discrete combinations of each pair of input parameters. In this case, there are two main categories: Colour and Shape. Under Colour, there are three subcategories: Red, Blue, and Green. Under Shape, there are two subcategories: Triangle and Circle. There is an additional category under Triangle labeled Size of triangle, with two subcategories: Small and Large. To test all pairs of these parameters, we need to use a tool or an algorithm that can generate the optimal test cases. One such tool is Pairwise.org, which can produce the following test cases:

Table

Colour

Shape

Size of triangle

Red

Triangle

Small

Blue

Circle

-

Green

Triangle

Large

Red

Circle

-

Blue

Triangle

Small

Green

Circle

-

Red

Triangle

Large

Blue

Triangle

Large

These eight test cases cover all pairs of parameters, such as Red-Triangle, Red-Small, Blue-Circle, etc. Therefore, the answer is B. 8. References = Pairwise Testing or All-Pairs Testing Tutorial with Tools and Examples, Pairwise Testing - What It Is, When & How to Perform?, All-pairs testing - Wikiwand, ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.2.3)

The minimum acceptable level of coverage for this use case is to cover all the scenarios and their combinations. Therefore, we need at least one test case for each of the following:

• Basic scenario single-sided to single-sided
• Alternative single-sided to double-sided
• Alternative copy of a set
• Alternative copy using the automatic document feeder
• Error no paper in paper tray
• Error paper jam
• Error out of staples References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 63, section 4.4.2.2.

Use cases are a test basis that describe the interactions between the users and the system in terms of scenarios. Use cases capture the functional requirements and the expected outcomes of the system. By visiting locations, spending time with expertusers, and walking through their scenarios, the test analyst is using use cases as the test basis. However, use cases do not provide enough information to validate that the transactions are realistic, such as the prices, discounts, taxes, and fees involved in the car buying process. This information is still missing and needs to be obtained from other sources, such as the business rules or the data model. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Use Case Testing - Tutorialspoint2, section “Use Case Testing”
• Use Case Testing: A Complete Guide3, section “What is Use Case Testing?”

1-switch coverage means that every possible transition from one state to another is tested at least once. Option C is the only test case that covers the transition from 2nd try to eat card, which is not covered by any other option. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 58, section 4.3.2.2.

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

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”

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

Functional completeness testing is a type of testing that verifies that all the user stories or requirements are implemented and tested according to the acceptance criteria. Traceability matrices are used to track the relationship between test cases and user stories, and to measure the test coverage of the user stories. Functional completeness testing is different from functional correctness testing, which checks if the system behaves correctly according to the specifications; functional appropriateness testing, which checks if the system provides functions that meet the user needs and expectations; and interoperability testing, which checks if the system can interact with other systems or components. References = ISTQB Certified Tester Advanced Level Syllabus Test Analyst, Section 1.1.1, Testing Process Tasks1; ISTQB Glossary, Terms: Functional Completeness Testing, Functional Correctness Testing, Functional Appropriateness Testing, Interoperability Testing2

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

The agile development model requires the earliest involvement from the test analyst because it is a flexible and iterative approach that delivers software in short cycles called sprints. The test analyst plays a key role in planning, designing, executing, and reporting on the testing activities for each sprint. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Understanding the SDLC: Software Development Lifecycle Explained3, section “Agile model”

Test analysis is the process of analyzing the test basis and defining the test objectives to establish the test conditions. Test conditions are the inputs and outputs that are used to define the scope and goals of testing. Identifying test conditions is one of the main activities of test analysis, as it determines what to test in terms of measurable coverage criteria. The other options are activities that occur during other phases of the test process, such as test planning, test implementation, or test execution. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Software Testing - Test Analysis - GeeksforGeeks2, section “Test Analysis”
• What is Test Analysis? - Software Testing Mentor3, section “What is Test Analysis?”

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

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”

The correct answer isD.Functional appropriateness.

Functional appropriateness

Functional appropriateness is the type of testing that ensures the application is suitable for the intended purpose and the user’s needs. It evaluates the relevance, usefulness, and user-friendliness of the application’s functions and features. In this case, the application should be tested for its suitability for senior citizens, who may have different preferences, expectations, and abilities than younger users.The interface should be easy to understand, navigate, and operate, and the application should provide adequate help and feedback to the users1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Functionality
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Functionality
• Usability Is Ageless: Conducting Usability Tests with Older Adults4, Section 1.1 Conceptualizing and Assessing Usability