Question 1

How many test cases are required to test a specification that has three conditions using a decision table testing which is not collapsed?

Options :

A : 2

B : 4

C : 6

D : 8

Answer: D

Question 2

Consider the simplified logic below for crediting money to a bank account.

Receive money and account number to be credited

IF account number is valid

IF customer account is active

Store current account balance as oldBalance

Credit money to account

IF oldBalance < zero

IF balance now >= zero

Set message "Overdraft cleared"

ELSE

Set message "A/c overdrawn"

ENDIF

ELSE

Set message = "You have more money"

ENDIF

IF account holder is VIP customer

Send message by email to customer

ENDIF

ELSE

Set message "A/c inactive"

Send message by email to supervisor

ENDIF

ELSE

Add 1 to count of invalid inputs

ENDIF

What percentage of decision testing coverage has been achieved by the following suite of test cases?

Test Case A - Account number valid, account is active, oldBalance = -100, balance now = +200, not a VIP

customer

Test Case B - Account number valid, account is active, oldBalance = -100, balance now = -50, is a VIP

customer

Options :

A : 40%

B : 60%

C : 70%

D : 80%

Answer: B

Question 3

If we say that a set of tests has achieved 100% structural decision coverage on a particular module in a

program, what does that mean?

Options :

A : That all bugs present in that module were necessarily revealed by those tests

B : That every control flow branch had been executed at least once by those tests.

C : That every dataflow in that module was exercised at least once by those tests.

D :

That every path through that module was exercised at least once by those tests.

Answer: B

Question 4

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

Options :

A : Fault seeding tools insert defects into the source code to check the effectiveness of testing.

B :

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

C :

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

D :

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

Answer: A

Question 5

Below is pseudo-code which calculates a customer's cruise credits based on past cruise history: PROGRAM CALC CRUISE CREDITS (CUST_ID) COUNT_CRUISES, CRUISE_CREDITS, LOYALTY_RATING: INTEGER CRUISE_LENGTH, CRUISE_ACCOM_TYPE: VAR LOYALTY_RATING = 0 COUNT_CRUISES = 0 CRUISE_LENGTH = 0 CRUISE_ACCOM_TYPE = 0 BEGIN READ CUSTOMER'S CRUISE HISTORY TO OBTAIN COUNT OF CRUISES READ CRUISE_HISTORY (CUST_ID) WHILE COUNT_CRUISES != -1 DO READ CUSTOMER'S NEXT CRUISE READ NEXT_CRUISE IF CRUISE_ACCOM_TYPE = 3 THEN CRUISE_CREDITS = CRUISE_CREDITS + 5 ELSE IF CRUISE_ACCOM_TYPE = 2 THEN CRUISE_CREDITS = CRUISE_CREDITS + 3 ELSE CRUISE_CREDITS = CRUISE_CREDITS + 2 ENDIF ENDIF COUNT_CRUISES = COUNT_CRUISES - 1 ENDWHILE LOYALTY_RATING = CRUISE_CREDITS / COUNT_CRUISES WRITE ("CRUISE CREDIT TOTAL IS:") WRITE (CRUISE_CREDITS) END PROGRAM CALC CRUISE CREDITS The code contains data flow anomalies on lines 14 and 27. Which examples of data flow anomalies can be found on these lines?

Options :

A :

Line 14: Cruise_Credits is not assigned a value (defined) before being used Line 27: Loyalty_Rating is defined but not subsequently used

B :

Line 14: Cruise_Credits is defined but not subsequently used Line 27: Loyalty_Rating is not assigned a value (defined) before being used

C :

Line 14: Cruise_Credits is re-defined before being used Line 27: Loyalty_Rating is defined but not subsequently used

D :

Line 14: Cruise_Credits should not be declared as an integer Line 27: Loyalty_Rating should be calculated within the While loop

Answer: C

Higher Test Marks with Free Online CTAL-TTA_Syll2019_UK Exam Practice

Buying Options: