ISTQB CTAL-TTA Exam Practice Test Instant Access

Question 1

Which of the following statements about fault seeding tools is correct?

AFault seeding tools insert defects into the source code to check the effectiveness of testing.

BFault seeding tools insert defects into the source code to test the input checking capabilities of the software.

CFault seeding tools insert defects into the source code to support the application of specification-based test design techniques.

DFault seeding tools insert defects into the source code to check the level of maintainability of the software.

Answer : A

Fault seeding is a method used to evaluate the effectiveness of a testing process. Tools designed for fault seeding intentionally insert known defects into the source code, which are then supposed to be discovered during testing. The main purpose is not to check the input checking capabilities, support specification-based test design techniques, or assess maintainability of the software, but rather to gauge how well the testing process can identify and capture defects. By comparing the number of seeded faults that are found against the total number of faults inserted, test teams can get an insight into the effectiveness of their testing strategies and coverage. This method helps in understanding the detection capabilities of testing efforts and in identifying potential areas for improvement in test processes.

Question 2

Consider the code fragment provided below:

The comment frequency of the code fragment is 13%.

To which non-functional quality characteristic does a good level of comment frequency especially contribute?

APortability

BMaintainability

CUsability

DPerformance Efficiency

Answer : B

The comment frequency in a code fragment relates to the number of comments in relation to the code size. A good level of comment frequency can significantly contribute to the maintainability of the software. Maintainability is a non-functional quality characteristic that refers to the ease with which a software system can be modified to correct defects, update features, improve performance or other attributes, or adapt to a changed environment. Comments in the code help developers understand the logic, purpose, and functionality of the code, which is crucial when modifications are required. This does not directly contribute to portability, usability, or performance efficiency, which are concerned with different aspects of the software's operation and user interaction.

Question 3

Consider the following specification:

If you are flying with an economy ticket, there is a possibility that you may get upgraded to business class, especially if you hold a gold card in the airline's frequent flier program. If you don't hold a gold card, there is a possibility that you will get 'bumped' off the flight if it is full when you check in late.

This is shown in the control flow graph below. Note that each box (i.e., statement, decision) has been numbered.

Three tests have been run:

Test 1: Gold card holder who gets upgraded to business class

Test 2: Non-gold card holder who stays in economy

Test 3: A person who is bumped from the flight

What is the level of decision coverage achieved by these three tests?

A60%

B67%

C75%

D80%

Answer : B

The control flow graph provided illustrates the decision points for an airline's upgrade and boarding process. Decision coverage is a measure of the percentage of decision points executed during testing:

Test 1 covers the decision points: Gold card? (Yes) and Business full? (No).

Test 2 covers: Gold card? (No) and Economy full? (No).

Test 3 covers the decision that leads to being bumped from the flight, which is Economy full? (Yes) and Business full? (Yes).

From the given tests, the decision points for Gold card? (No) and Business full? (No) are not tested, leaving us with 4 out of 6 decision points covered, which is approximately 67% decision coverage.

Question 4

Consider the code fragment provided below:

How many test cases are needed for the code fragment lines 26 - 37 to achieve 100% modified condition/decision coverage?

A2 test cases

B4 test cases

C6 test cases

D8 test cases

Answer : B

Modified condition/decision coverage (MC/DC) requires each condition in a decision to be shown to independently affect the decision's outcome. For the code fragment provided, we have three independent conditions that need to be evaluated both as true and false. The minimum number of test cases needed to satisfy MC/DC for three conditions is four, which would allow each condition to be shown to independently affect the outcome of the decision.

Question 5

You are asked to provide a practical and pragmatic testing solution for a commercial system where the main user interface is via the Internet. It is critical that the company's existing good name and market profile are not damaged in any way. Time to market is not a critical issue when appropriate testing solutions are identified to mitigate business risks.

A product risk assessment has revealed the following product risk:

* Abnormal application termination due to connection failure of the main interface.

Which of the following is the appropriate test type to address this risk?

APerformance efficiency testing

BPortability testing

CReliability testing

DOperability testing

Answer : C

Reliability testing is the process of checking whether the software consistently performs according to its specifications. For a commercial system with a critical internet-based user interface, ensuring that the application can handle connection failures without abnormal terminations is essential. Reliability testing would include testing the system's ability to recover from failures and continue operating, which directly addresses the risk identified.

Question 6

Which of the following does NOT contribute to a more effective review preparation by the Technical Test Analyst?

AEnsure that participants spend enough time during preparation, e.g.. by managing checking rate (number of pages checked per hour during review preparation).

BManaging logging rate (number of defects logged per minute during the meeting).

CThe usage of review checklists.

DReview training for the Technical Test Analyst.

Answer : B

An effective review preparation by a Technical Test Analyst includes ensuring that participants are well-prepared and that they spend enough time on preparation, which can be managed by checking the rate (option A). The use of review checklists (option C) and providing review training (option D) are also methods that contribute to more effective review preparation. However, managing the logging rate (option B), or the number of defects logged per minute during the meeting, is not related to the preparation phase but rather to the defect detection and logging phase during the actual review meeting. It is not a preparation activity but a review execution activity.

Question 7

A major Caribbean bank typically develops their own banking software using an Agile methodology. However, for some specific components COTS software is acquired and used. The bank does not want to create a dependency on any external COTS supplier.

As part of the test approach, portability testing will be performed. Which portability sub-characteristic is especially relevant for the Caribbean bank?

AIn stall ability

BAdaptability

CReplaceability

DCo-existence

Answer : C

Portability testing is concerned with how well software can be transferred from one environment to another. In the context of a bank using COTS (Commercial Off-The-Shelf) software, the sub-characteristic of replaceability becomes particularly relevant. This is because the bank does not want to create a dependency on any external COTS supplier, meaning it should be able to replace the software with another product without significant effort or operational disruption. Replaceability ensures that if needed, the bank can switch to different software, thereby mitigating the risk of supplier dependency.

ISTQB Certified Tester Advanced Level Technical Test Analyst Exam Practice Test