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

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

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

 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 equivalence partitions are based on the size of the carpet purchase and the installation price. There are four possible sizes: small, medium, large, and extra large. There are three possible prices: $5, $4, and $2 per square yard. The smallest set of test conditions that covers all the equivalence partitions is to test each size with its corresponding price, plus a no purchase scenario. Option C is the only one that does that. Option A does not test the large and extra large sizes. Option B does not test the extra large size. Option D tests more than the minimum required. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 50, section 4.1.2.2.

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

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

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”

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”

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

Use cases can be used for performance testing to measure the response time and throughput of the system under different workloads and scenarios. Use cases describe the process flows through the system based on its most likely use, which can help to simulate realistic user behavior and identify potential bottlenecks and performance issues.

References =

• ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.2.2, page 411
• How to write a performance test case | MyLoadTest2
• Performance Testing Types, Steps, Best Practices, and Metrics - Stackify3

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 diagram must be tested. The state diagram has seven states: Login, Menu, Logout, Withdraw, Deposit, Get Balance, and Access Account. There are 13 transitions in the state diagram, as shown by the arrows. Therefore, 13 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”
• State Transition Testing - Tutorialspoint3, section “State Transition Diagram”

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

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

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

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.

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