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

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

The correct answer isD.Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed.

A.Enter your exploratory test cases with detailed test steps into the Test Management System

This is incorrect because entering the test cases into the Test Management System is not enough to document and track the exploratory testing process. The test cases should also include the expected results, actual results, and defects found during the testing. Moreover, the test cases should be organized into a clear and logical structure that reflects the test charter and scope.

B.Close the session and start a new session with a new charter

This is incorrect because closing and starting a new session with a new charter would mean losing all the information and data collected during the previous session. This would make it difficult to resume and continue the testing process from where it left off. Instead, it would be better to use a consistent and stable session with a single charter that covers all the requirements and features of the system.

C.Continue the session and conduct the testing for debit cards

This is incorrect because continuing the session and conducting only one type of card (debit) would not provide a comprehensive coverage of all possible scenarios and outcomes of accepting credit cards. It would also limit the scope of testing to only one aspect of payment processing, which may not reflect all the business rules, validations, exceptions, or integrations involved in this domain.

D.Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed

This is correct because automating some or all of the exploratory tests can help to save time, effort, and resources by reducing manual effort and increasing efficiency. It can also help to improve accuracy, consistency, and reliability by eliminating human errors and biases. Moreover, automating some or all of the exploratory tests can enable them to be reused for confirmation testing after fixing any defects found during exploratory testing.Confirmation testing is a type of functional testing that verifies that all requirements are met by performing regression tests on previously tested functionality1.

The test conditions are the inputs and outputs that are used to define the scope and objectives of testing. They should be understandable by business stakeholders because they affect their expectations and satisfaction with the software product. Business stakeholders can provide valuable feedback to the test analyst on the test conditions, such as clarifying any ambiguities, suggesting any changes, or identifying any gaps or risks. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Who are the stakeholders in software testing? How to identify them?3, section “Stakeholders in testing will require attention”

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.

The specification does not clearly define the dependencies between the power unit and the body style options. For example, it is not clear if the user can select a hybrid power unit and then choose a saloon body style, or if the hybrid option is only available after selecting a hatchback body style. Similarly, it is not clear if the user can select an SUV body style and then choose a hybrid power unit, or if the SUV option is only available with petrol or diesel power units. These dependencies affect the usability of the site, as they may confuse the user or limit their choices. The specification should specify the valid combinations of power unit and body style, and how the site will handle invalid or unavailable combinations. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 80, section 5.3.2.1.

The iterative model is a cyclical process in which the software product is developed and tested incrementally in short cycles called iterations. Each iteration delivers a working version of the product that can be evaluated and improved. Compared to the V-model, which is a linear and sequential process that follows a fixed set of phases and activities, the iterative model requires a reduced set of standard test processes for each iteration, as well as more flexibility and adaptability to changing requirements and feedback. The test analyst and the test team might expect to make this adjustment when working on an iterative model project. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• What is an iterative approach and what are its benefits?2, section “What is agile, iterative development, or the PDCA cycle?”
• Iterative Model (Software Engineering) - javatpoint3, section “Iterative Model”

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

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)

Functional correctness testing is a type of testing that verifies whether the system or software performs its intended functions correctly and accurately, according to the specified requirements. It can detect defects such as non-compliance to requirements, calculations that produce incorrect results, and improper handling of data or situations. References = Functional Testing: What Is It, Types, Best Practices, Tools (Section 1.1), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.1.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

Test conditions are the inputs and expected outputs of a test case, based on the requirements. To identify the test conditions from REQ2 and REQ3, we need to consider all the possible combinations of the categories of hours exposed to the sun (A, B, C) and the labels of sun intensity (low, medium, high, extreme). There are 12 such combinations in total. However, the three test cases given only cover 3 of them: A-low, C-medium, and A-low. Therefore, there are 9 test conditions that are not covered by the test cases. However, some of these test conditions are invalid or impossible, such as A-extreme or C-low, because the sun intensity is correlated with the hours exposed to the sun. Therefore, we need to exclude these invalid test conditions from the count. According to the Skin Cancer Foundation, the sun intensity is usually low before 10 a.m. and after 4 p.m., medium between 10 a.m. and 1 p.m., high between 1 p.m. and 4 p.m., and extreme between 10 a.m. and 4 p.m. in the summer or at high altitudes. Based on this information, we can assume that the valid test conditions are:

• A-low
• A-medium
• B-medium
• B-high
• C-high
• C-extreme

These six test conditions are not covered by the three test cases, so the answer is C. 6. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.2.1), Be Safe in the Sun (Section 2.1)

A decision table is a technique that shows the possible combinations of conditions and actions for a given problem. To achieve 100% coverage of the decision table, all the combinations of conditions must be tested. The decision table has four conditions: debit card valid, PIN valid, amount approved, and dates available. Each condition has two possible values: yes or no. Therefore, the number of test cases for the decisiontable is 2^4 = 16. However, some of these test cases are invalid or redundant, as they do not reflect the logic of the problem. For example, if the debit card is not valid, then the PIN and the amount are irrelevant. Similarly, if the PIN is not valid, then the amount is irrelevant. Therefore, these test cases can be eliminated from the decision table. After eliminating the invalid or redundant test cases, only eight test cases remain, as shown in the table below:

Table

Debit card valid

PIN valid

Amount approved

Dates available

Actions

No

No

No

No

Reject reservation

No

No

No

Yes

Reject reservation

No

No

Yes

No

Reject reservation

No

No

Yes

Yes

Reject reservation

Yes

No

No

No

Reject reservation

Yes

No

No

Yes

Reject reservation

Yes

No

Yes

No

Reject reservation

Yes

No

Yes

Yes

Reject reservation

Yes

Yes

No

No

Prompt for lower purchase

Yes

Yes

No

Yes

Prompt for lower purchase

Yes

Yes

Yes

No

Prompt for different date

Yes

Yes

Yes

Yes

Create reservation

References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Decision tables - IBM2, section “Decision table overview”

 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 test basis is the collection of documents that provide the basis for testing, such as requirements, design documents, user manuals, etc. The test analyst examines the test basis to understand the scope and objectives of testing, as well as the risks and assumptions involved. This task is performed during the test analysis phase, which is the first phase of the test process. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Test Analysis and Test Design are key for software testing3, section “Test Analysis”

The correct answer isA.Functional correctness testing.

Functional correctness testing

Functional correctness testing is the type of testing that measures the degree of accuracy in a mortgage rate calculation module of the software you are testing. It verifies that the module produces the correct results for different inputs and scenarios, such as different interest rates, loan terms, payment frequencies, etc.It also checks that the module complies with the specifications and requirements of the mortgage rate calculation1.

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

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 use case only describes the normal or happy path scenario, where the user performs a successful cash withdrawal. However, it does not consider any alternative or exceptional scenarios, such as invalid card, incorrect PIN, insufficient balance, network failure, etc. These scenarios are important to test the robustness and reliability of the ATM system, and should be included in the use case specification. References = ISTQB Certified Tester Advanced Level Syllabus Test Analyst, Section 2.2.1, Use Case Testing1; ISTQB Advanced Level Test Analyst (CTAL) Exam Study Guide, Section 2.2.1, Use Case Testing2

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

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 table must be tested. There are eight transitions in the state table, as shown by the arrows. Therefore, eight 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”
• 0 and 1 - Switch Coverage in State Transition Testing?3, answer by Marco Filippone

The correct answer isB.The information exchange between each system and its environment.

The information exchange between each system and its environment

The information exchange between each system and its environment refers to the compatibility and functionality of the systems with respect to the hardware, software, network, and other external factors that may affect their interaction.This type of testing is important to ensure that the systems can operate smoothly and reliably in different scenarios and conditions1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Interoperability
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Interoperability
• A Simple Guide to Interoperability Testing (with Examples)4, Section 2. How to do Interoperability testing