Free CTFL_Syll2018 – Certified Tester Foundation Level (Syllabus 2018) Practice Test Question

Select an option, then click Submit answer.

• ○

  How to fix the defect
  

• ○

  Severity and priority
  

• ○

  Test environment details
  

• ○

  How to reproduce the defect
  
  
  

Select an option, then click Submit answer.

• ○

  Technical Review
  

• ○

  Inspection
  

• ○

  Walkthrough
  

• ○

  Informal review
  
  
  

Select an option, then click Submit answer.

• ○

  It is a project risk since successful completion of the project depends on successful and timely completion of the tests
  

• ○

  It is a product risk since any risk associated with development timelines is a product risk
  

• ○

  It is a product risk since default on part of the sub-contractor may lead to delay in release of the product

• ○

  It is no longer a risk for the Test Manager since an independent party (the sub-contractor) is now managing it
  
  
  

Select an option, then click Submit answer.

• ○

  Test plan
  

• ○

  Project plan
  

• ○

  Test design specification
  

• ○

  Requirements specification
  
  
  

Select an option, then click Submit answer.

• ○

  II, III, IV, V
  

• ○

  l, III IV
  

• ○

  I, II. Ill
  

• ○

  I, ll
  
  
  

• ○

  Designing and prioritizing test cases
  
  II Identifying any required infrastructure and tools
  
  III. Reviewing the test basis
  
  IV Creating test data and preparing test harnesses
  

• ○

  Writing automated test scripts
  

Select an option, then click Submit answer.

• ○

  Evaluating test criteria and reporting
  

• ○

  Test implementation and execution
  

• ○

  Test planning and control
  

• ○

  Test analysis and design
  
  
  

Select an option, then click Submit answer.

• ○

  Detection of failures not easily found by other types of testing
  

• ○

  Early defect detection
  

• ○

  Detection of suspicious operations caused by deviations from regulations
  

• ○

  Detect deviations in standards by executing the source code
  
  
  

Select an option, then click Submit answer.

• ○

  Finding defects
  

• ○

  Providing information for decision-making
  

• ○

  Analyzing and removing the cause of failures
  

• ○

  Gaining confidence about the level of quality of the software
  
  
  

Select an option, then click Submit answer.

• ○

  Checking that all decisions have been exercised in a single program
  

• ○

  Checking that all decisions have been exercised in a business process
  

• ○

  Checking that all calls from one program module to another have been made correctly
  

• ○

  Checking that at least 50% of decisions have been exercised by a test case suite
  
  
  

Select an option, then click Submit answer.

• ○

  Migration of software onto a new platform
  

• ○

  Testing during initial development of a replacement for an existing system

• ○

  Purchase of a new software tool
  

• ○

  Updating of a regression suite
  
  
  

Select an option, then click Submit answer.

• ○

  Dynamic test design
  

• ○

  Data-driven
  

• ○

  Keyword-driven
  

• ○

  Data coverage analysis
  
  
  

Select an option, then click Submit answer.

• ○

  Testing can demonstrate that there are no defects
  

• ○

  Testing can demonstrate that there are defects

• ○

  Testing can demonstrate that the software is correct
  

• ○

  Testing can demonstrate that there are no hidden defects in the software
  
  
  

Select an option, then click Submit answer.

• ○

  unit test framework tool evelopers who are familiar with the system's structure.
  

• ○

  configuration management tool
  

• ○

  test design tool
  

• ○

  monitoring tool
  
  
  

Select an option, then click Submit answer.

• ○

  Re-prioritize tests because of time pressure
  

• ○

  Change the test schedule due to viability of a test environment
  

• ○

  Writing test suspension and resumption criteria in the test plan
  

• ○

  Set an entry criterion requiring fixes to be retested by a developer before accepting them into a build
  
  
  

Select an option, then click Submit answer.

• ○

  Pair programming is done with developer and tester pairing together
  

• ○

  Pair programming is an alternative term for code inspection.
  

• ○

  Pair programming is used usually in waterfall model
  

• ○

  Pair programming is, among other things, an informal review method.