CTAL-TA_Syll2019 Practice Exam Questions with Answers ISTQB Certified Tester Advanced Level - Test Analyst (Syllabus 2019) Certification

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

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)

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”

Classification trees are a visual way of identifying test objects and data, and pairwise testing is a technique of generating test cases that cover all possible pairs of values from different classifications. Classification trees support pairwise testing by:

• Helping to identify inputs to be used by the pairwise test technique, as each class represents a possible value for a test parameter.
• Showing the combinations needed to cover all-pairs, as each test case is a selection of one class from each classification.
• Helping to identify particular combinations of interest, as the test engineer can use the tree structure to group or prioritize classes based on their relevance or risk. References = ISTQB Advanced Level Test Analyst Syllabus 2019, section 3.2.3; Smarter Test Design with Classification Trees and Pairwise Techniques, slides 6-12.

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?

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”

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

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

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?

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.

Installability testing is a type of non-functional testing that focuses on verifying that the software can be installed, upgraded, and uninstalled without errors or interruptions1. It is usually performed by a technical test analyst who has knowledge of the installation requirements, dependencies, and configurations2. The main objectives of installability testing are to ensure that the software is compatible with different platforms, environments, and hardware specifications, and that the installation and de-installation processes are functional, reliable, and secure3. Usability issues, such as the clarity, simplicity, and efficiency of the installation and de-installation user interfaces, are not the primary concern of installability testing, and may be better addressed by other types of testing, such as usability testing or user acceptance testing4. References = Installation testing - Wikipedia; ISTQB Advanced Level Technical Test Analyst Syllabus 2019, section 4.3.2; Mastering Installability Testing: A Key Software Quality Assurance Process; Installation Testing | Complete Overview Of Installation 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 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”.

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”

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”

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

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