iSQI CTAL-TA_Syll2019 Dumps

A system architecture document is a document that describes the structure and behavior of a system, including its components, interfaces, communication protocols, and dependencies. It is typically used by a Test Analyst as the test basis for interoperability testing, as it provides the necessary information to design test cases that cover the interactions between different systems or components. A system architecture document can also help to identify potential risks and challenges related to interoperability testing, such as compatibility issues, performance bottlenecks, security vulnerabilities, and data integrity problems. References = Interoperability Testing in Software Testing (Section 2.2), A Simple Guide to Interoperability Testing (with Examples) (Section 2.3), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.3.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”

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

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?

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.

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

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”

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

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”

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

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 correct answer isD.The story contains more than one item of functionality.

The story contains more than one item of functionality

A user story should be small, simple, and focused on one item of functionality that delivers value to the user. This story combines two items of functionality: querying the balance and withdrawing money. These items could be separated into two different stories, each with its own acceptance criteria and priority.This would make the stories easier to understand, estimate, test, and deliver1.

References=

• User Stories | Examples and Template | Atlassian2, Section User story best practices
• ISTQB Certified Tester Advanced Level Syllabus Test Analyst3, Section 2.1.1 Test Analyst Tasks in the Test Process
• ISTQB Test Analyst Syllabus and Study Guide4, Section 2.1.1 Test Analyst Tasks in the Test Process

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

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

The correct answer isA.Functional testing.

Functional testing

Functional testing is the type of testing that focuses on completeness, appropriateness, and correctness characteristics of the application under test. Completeness means that all the functions and features of the application are tested. Appropriateness means that the functions and features are suitable for the intended purpose and meet the user’sneeds.Correctness means that the functions and features produce the expected results and do not contain any errors or defects1.

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