CTFL MCQs

CTFL MCQs

These CTFL multiple-choice questions and their answers will help you strengthen your grip on the subject of CTFL. You can prepare for an upcoming exam or job interview with these 30 CTFL MCQs.
So scroll down and start answering.

1: A functional testing approach in which test cases are designed based on business processes.

A.   Business process-based testing

B.   COTS

C.   Conformance testing tools

D.   LCSAJ testing

2: Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes

A.   Test planning Tasks

B.   Independence of testing

C.   Defect masking

D.   Test execution tasks

3: Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers

A.   Test levels

B.   Conformance testing tools

C.   Incident description subheadings

D.   Configuration management tools

4: A set of conditions that a system needs to meet in order to be accepted by end users

A.   Data flow structure

B.   Acceptance criteria

C.   Contract acceptance testing

D.   Exploratory testing

5: Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.

A.   Dynamic analysis tools

B.   Entry criteria

C.   Contract acceptance testing

D.   Functional incremental integration

6: Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.

A.   Conformance testing tools

B.   Data flow structure

C.   Incident report

D.   Defect density

7: Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.

A.   Fault attack

B.   Stub

C.   Accuracy

D.   Incremental testing

8: Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.

A.   Impact

B.   Multiple condition coverage

C.   Environmental needs

D.   Experience-based techniques

9: A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.

A.   Condition coverage

B.   Big-bang testing

C.   Resolution types

D.   Functional testing

10: A task of maintaining and controlling changes to all entities of a system.

A.   Configuration management

B.   Test log uses

C.   Exhaustive testing

D.   Error guessing

11: Sequence in which data items are accessed or modified by code.

A.   Defect

B.   Boundary value analysis

C.   Data flow structure

D.   Component testing

12: Incident Report - Identifier - Summary - Incident - Description - Impact

A.   Input specifications

B.   Equivalence partitions

C.   IEEE incident report template

D.   Fault attack

13: Integrate different kinds of tools to make test management more efficient and simple.

A.   Nonfunctional requirements

B.   Incident report

C.   Component testing

D.   Integration management tools

14: Sequence in which instructions are executed through a component or system

A.   Waterfall model phases

B.   Cyclomatic complexity

C.   Waterfall model benefits

D.   Control flow structure

15: Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).

A.   Incident description subheadings

B.   Configuration management tools

C.   Keyword-driven testing

D.   Data-driven testing

16: Software products or applications designed to automate manual testing tasks.

A.   Automation tools

B.   SW development model

C.   Environmental needs

D.   Ad hoc integration

17: Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.

A.   Decision testing

B.   Business process-based testing

C.   Test condition

D.   Multiple condition coverage

18: Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations

A.   Agile software development model

B.   Cyclomatic complexity

C.   Acceptance testing

D.   Risk-based testing

19: Tools used by developers to identify defects in programs.

A.   Experience-based techniques

B.   Defect masking

C.   SW development model

D.   Debugging tools

20: Input or combination of inputs required to test software.

A.   Conditions

B.   Functional incremental integration

C.   Three main SW development models

D.   Test data preparation tools

21: Operational testing performed at an _external_ site without involvement of the developing organization.

A.   Contract acceptance testing

B.   Resolution types

C.   Beta testing

D.   Exploratory testing

22: Component - Integration - System - Acceptance

A.   Test levels

B.   Horizontal traceability

C.   Actual result

D.   Integration

23: One defect prevents the detection of another.

A.   Defect masking

B.   Integration management tools

C.   Stub

D.   Big-bang testing

24: All possible combinations of input values and preconditions are tested.

A.   Component integration testing

B.   COTS

C.   Interoperability testing

D.   Exhaustive testing

25: A review not based on a formal documented procedure

A.   Independence of testing

B.   Informal review

C.   Failure

D.   IEEE incident report template

26: A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram

A.   Big-bang testing

B.   Data flow structure

C.   Impact

D.   Cause-effect graphic testing

27: Special additions or changes to the environment required to run a test case.

A.   Equivalence partitioning

B.   Inspection

C.   Environmental needs

D.   Input specifications

28: An event or item that can be tested using one or more test cases

A.   Dynamic analysis tools

B.   Configuration management tools

C.   Testing process phases

D.   Test condition

29: Record details of test cases executed Record order of execution record results

A.   Documentation tools

B.   Decision table

C.   Test log uses

D.   Contract acceptance testing

30: Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)

A.   Test planning Tasks

B.   Documentation tools

C.   Alpha testing

D.   Coverage measurement tools