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

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

The test execution phase involves running the test cases and comparing the actual results with the expected results. The test analyst is responsible for analysing any anomalies or deviations from the expected results and determining their root causes. This task helps to identify defects, report them, and track their resolution. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• STLC (Software Testing Life Cycle) Phases, Entry, Exit Criteria2, section “Test Execution Phase”
• Test Execution Tutorial: Detailed Guide With Best Practices3, section “Activities of Test Execution”

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

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

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

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

The classification tree shows the combinations of power units and body styles for the Supercar online vehicle sales website. Since SUVs are not available in hybrid, and the existing test cases already cover petrol SUV, electric saloon, and petrol hatchback, the missing test case is hybrid hatchback to achieve minimum class coverage. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, Section 3.2.3, Classification Trees1; ISTQB Advanced Level Test Analyst (CTAL) Exam Study Guide, Section 3.2.3, Classification Trees2

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

User experience (UX) is a broad term that encompasses the overall impression and satisfaction that a user has when interacting with a software product. It includes aspects such as value, desirability, adaptability, and usability. Usability is a specific aspect of UX that focuses on how easy, efficient, and error-free it is for a user to perform a task or achieve a goal with the product. Usability is a necessary but not sufficient condition for a good UX. A product can be usable but not desirable, or desirable but not usable. References = ISTQB Certified Tester Advanced Level Syllabus Test Analyst, Section 3.1.1, Usability and User Experience Testing1; Usability vs. User Experience: What’s the Difference? - HubSpot Blog, Section Usability vs. User Experience

The smallest set of test conditions to provide minimum coverage of the boundary values is the one that tests the minimum and maximum values for each category of carpet installation prices, as well as the values that are just above or below the boundaries. Option A covers these values, as it tests the boundary values of 0, 20, and 40 square yards, as well as the values that are one square yard more or less than these boundaries. It also tests the maximum possible value for the carpet area and the value that exceeds it. The other options do not test all the boundary values or have redundant values. References =

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

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 medical domain application that is undergoing frequent changes, it is advisable to use low-level test cases that provide more details and specifications for each feature. Low-level test cases can support both the external audit and the new junior testers by ensuring traceability between the requirements and the test scenarios, as well as by facilitating future changes or enhancements. Low-level test cases can also be reviewed and updated by both experienced domain-based testers and junior testers who have extensive knowledge of the medical domain. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Healthcare Domain Testing: 60 Sample Test Case Examples3, section “Testing Types for Healthcare Applications”

A usability review is a technique that evaluates the usability of a system or product based on a set of criteria or heuristics, without involving the actual users. It can be performed by experts or peers, and it can identify potential usability problems and suggest improvements. A usability review is suitable for situations where the availability of users is limited or impractical, and it can provide quick and low-costfeedback. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 81, section 5.3.2.2.

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

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”

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

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

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”