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

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.Execute test case A on iOS and Android (latest version) using FireFox (latest version).

Execute test case A on iOS and Android (latest version) using FireFox (latest version)

This is an example of an adaptability test that should be executed by a Test Analyst because it tests the compatibility and functionality of the system across different platforms, devices, and browsers.It verifies that the system can work correctly and reliably in various environments and scenarios that the users may encounter1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Adaptability
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Adaptability
• Adaptability Test - Candidate Screening Assessment | HiPeople4, Section 1. What is the Adaptability Test?

The correct answer isA.The user should not experience an error that does not have a clear explanation and instructions for correction.

The user should not experience an error that does not have a clear explanation and instructions for correction

User error protection is the degree to which a system protects users against making errors. It includes providing clear and helpful error messages, preventing or minimizing the consequences of errors, and allowing users to recover from errors.In this case, the test condition verifies that the application provides adequate feedback and guidance to the user when an error occurs, such as entering an invalid word, losing network connection, or encountering a system failure1.

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 - ISO 250004, Section User error protection

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 risk impact is the measure of the potential negative consequences of a risk item on the project objectives. It depends on the severity of the defect, the frequency of occurrence, and the visibility to the stakeholders. Since requirement R1 is business critical, any failure in meeting this requirement would have a significant impact on the customer satisfaction, the reputation of the organization, and the legal compliance. Therefore, the risk impact for requirement R1 should be categorized as high or very high, regardless of the likelihood of occurrence. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Risk Based Testing: Approach, Matrix, Process & Examples2, section “Risk Impact Assessment”
• What is Risk Based Testing: With Best Practices3, section “Risk Impact Analysis”

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.

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.

Test set (i) is the best option as it tests the boundary condition of a salary of less than €20,000 and being married, with a varying number of children including the boundary value of three children. This test set covers the minimum and maximum values for the salary and the number of children, as well as the nominal values. The other test sets donot test the boundary value of the salary or the number of children fully, as they either omit or repeat some 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”

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

 Equivalence partitioning is a black-box test technique that divides the input domain of a system into partitions of equivalent data. Boundary value analysis is a technique that tests the boundaries of these partitions, where errors are more likely to occur. These techniques are suitable for testing the processing functionality of a critical traffic control system, as they can ensure that the system handles the input variables within the defined ranges and detects any invalid or out-of-range values. References = Black Box Testing Techniques: A Comprehensive Guide (Section 5.1 and 5.2), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.2.1 and 3.2.2)

Pairwise testing is a test design technique that reduces the number of test cases needed to cover all possible combinations of input parameters, by testing only pairs of parameters at a time. It is based on the assumption that most defects are caused by interactions of at most two factors. Pairwise testing is suitable for testing systems that have multiple parameters with discrete values, such as browsers, plug-ins, servers, and operating systems. It can help to find defects that are related to the compatibility and interoperability of the system in different environments. References = ISTQB Advanced Level Test Analyst Syllabus 2019, section 3.2.3; Pairwise Testing or All-Pairs Testing Tutorial with Tools and Examples; Test Design Techniques, section 5.4.

Interoperability is the degree to which two or more systems or components can exchange and use information. It is a crucial quality characteristic for an e-commerce product that needs to interface with backend applications, such as finance, stock control and order delivery. The test plan must include tests to verify that the COTS package can communicate and integrate with the existing systems and applications, and that the data and functionality are consistent and accurate across the interfaces. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 10, section 1.2.2.2.

Experience-based test techniques rely on the tester’s knowledge, intuition, and creativity to design and execute tests. They are useful when there are no or poor specifications, limited time, or high-risk areas. Examples of experience-based test techniques are error guessing, exploratory testing, and checklist-based testing. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 67, section 4.5.2.2.

The correct answer isD.User acceptance testing.

User acceptance testing

User acceptance testing (UAT) is the type of testing that focuses on high-level business cases and ensures that the system meets the user’s needs and expectations. It is usually conducted in the software development lifecycle after the system integration testing and before the deployment.UAT involves real users or stakeholders who validate the functionality, usability, and reliability of the system in a realistic environment1.

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
• User Acceptance Testing: A Complete Guide4, Section 1. What is User Acceptance Testing?

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 isB.The acceptance criteria are not testable.

The acceptance criteria are not testable

The acceptance criteria are not testable because they are vague and subjective. They do not specify any measurable or observable outcomes or conditions that can be verified by the test analyst.For example, what does “as fast as possible” or “easily” mean in terms of performance and usability? How can the test analyst determine if the user does not leave during the transaction or if they log in easily? The acceptance criteria should be rewritten to include clear and quantifiable criteria, such as response time, error rate, user satisfaction, etc1.

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
• What is User Story and Acceptance Criteria (Examples)4, Section 2. What is Acceptance Criteria?

A decision table is a technique that shows the possible combinations of conditions and actions for a given problem. A decision table that is not collapsed has one test case for each combination of conditions, regardless of whether the actions are the same or different. The tax system specification has three conditions: salary less than €20,000, married, and number of children between three and four. Each condition has two possible values: true or false. Therefore, the number of test cases for a non-collapsed decision table is 2^3 = 8. References =

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

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”

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.

Risk mitigation is the process of implementing actions to reduce the probability and/or impact of risks1. When you execute the tests in priority order based on the risk ratings, you are performing risk mitigation, as you are trying to prevent or minimize the potential failures and defects in the system2. Risk planning, identification, and assessment are the previous steps in the risk management process, which help to prepare for risk mitigation3.

References = 1: Risk Mitigation – Planning, Implementing, and Monitoring 2: Risk Based Testing Approach for Agile Teams 3: The Ultimate Guide to Risk Based Testing: Risk Management in Software Testing