ISTQB CTAL-TTA Value Pack (Frequently Bought Together)

You are working on a project to develop an application that allows users to collaborate via bespoke, online whiteboards. The first release, delivering core functionality, highlighted misunderstandings of the user stories between testers, developers and the product owner during sprint development Since that release, the developers have agreed to implement a TDD approach for future software development.
Creation of the product backlog for the second release is underway and you have recommended to the project stakeholders that an atdd approach be adopted for the backlog's user stories. What would be a GOOD REASON for making this recommendation?
SELECT ONE OPTION

• A. The test strategy states that automation shall be used to minimize effort for execution of acceptance tests
• B. The team wants to start using BDD and therefore atdd must also be used
• C. TDD can only work effectively when an ATDD approach is used for the user stories use of attd examples will help address the misunderstandings encountered in release 1

You are a Technical Test Analyst preparing load test scripts. You have been invited to a technical review of the system's operational profile document produced by the business. The meeting is next week, during your preparation you notice that volumetric data covering projected transaction volumes will be held in a separate document that will not be available before the meeting. What would be the BEST course of action?

• A. Delay the review but limit schedule impact by presenting the volumetric document to the reviewers during the meeting
• B. State that you are not a mandatory reviewer but request that both documents be sent to you once agreed
• C. Request that the meeting be delayed until the volumetric document has been drafted and examined by the reviewers
• D. To avoid delay to the project, attend the review as scheduled and raise the issue at the meeting

You are working on a project that is integrating code from multiple development groups. There have been numerous integration problems, particularly regarding reliability, error recovery and transactional integrity.
You are now responsible for planning the performance efficiency testing for this product. There Is a strong feeling among the development managers that some parts of the code are weaker than others and will tend to exhibit problems during the performance efficiency testing. To identify these problematic areas as soon as possible, which type of testing should you do?

• A. Scalability testing
• B. Interoperability testing
• C. Load testing
• D. Stress testing

A review of the following pseudo code is to be performed using a checklist:
Module Vowel Counter
Message: array of Characters
M, N: Integer
ACount, ECount, ICount, OCount, UCount: Integer
BEGIN
I=1
Read Nextchar
While Nextchar <> 'S'
DO
Message (I) = Nextchar
I = I+1
Read Nextchar
ENDWHILE
FOR M = 1 To I
DO
Print (Message(M))
IF Message (M) = 'E'
THEN
ECount = ECount + 1
ELSE
IF Message (M) = 'A'
THEN
ACount = ACount + 1
ELSE
IF Message (M) = 'I'
THEN
ICount = ICount + 1
ELSE
IF Message (M) = 'O'
THEN
OCount = OCount + 1
ELSE
IF Message (M) = 'U'
THEN
UCount = UCount + 1
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
ENDFOR
Print ('Message contains ' ACount + ECount + ICount + OCount + UCount ' vowels') END Which of the following checklist items would find code errors in this scenario?
A) Are all variables properly declared?
B) Are all loops, branches, and logic constructs complete, correct, and properly nested?
C) Are all cases covered in an IF-ELSEIF, including ELSE or DEFAULT clauses?
D) Are loop termination conditions obvious and invariably achievable?
E) Are there any redundant or unused variables?

• A. c and d
• B. a and d
• C. b and c
• D. a and e

As Technical Test Analyst on a test automation project covering the acquisition of a commercial test execution tool, what would you MOST likely be responsible for?

• A. Determining who will execute the automated tests
• B. Approving the estimated costs for implementing the test automation project
• C. Creating and supplying the data to be accessed by keyword-driven automation scripts
• D. Defining the business processes that will be used for keyword-driven testing