CTAL-TA_Syll2019 Exam Dumps - iSQI ISTQB CTAL-TA_Syll2019 Questions and Answers

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

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)

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?

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)

Functional appropriateness is the degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions1. It is typically tested during system testing, which is the process of testing an integrated system to verify that it meets specified requirements2. System testing is conducted after component testing and before acceptance testing, and it covers both functional and non-functional aspects of the system3. References = ISO 25010, section A.1; ISTQB Advanced Level Test Analyst Syllabus 2019, section 1.3.1; Test Automation Fundamentals, section A.1.

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

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

State transition testing is a technique that tests the behaviour of a system or component based on its transitions between states in response to events. It is suitable for testing systems that have complex interactions and dependencies, such as a car navigation system that needs to integrate with other car software components. State transition testing can verify the functional correctness of the system by checking if it responds correctly to different inputs and events, and if it reaches the expected states and outputs. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 54, section 4.2.2.2.

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