Free TM12 – ISTQB-BCS Certified Tester Advanced Level- Test Manager (2012) Practice Test Question

Select all that apply, then click Submit answer.

• ○

  Number of defects found during the requirements review.

• ○

  Total number of defects attributable to requirements found during unit, integration, system and acceptance testing.

• ○

  Total number of defects found during functional specification review, high-level design review, low-level design review, code review, unit testing, integration testing, system testing and acceptance testing.

• ○

  Time to conduct the requirements review.

• ○

  Total number of defects attributable to requirements, found during functional specification review, high-level design review, low-level design review, code review, unit testing, integration testing, system testing and acceptance testing.
  
  

Select all that apply, then click Submit answer.

• ○

  Does the tool support all the types of code coverage required from the three levels A, B, C of the DO-178B standard?

• ○

  Does the tool have a good general usability?

• ○

  What are the costs to qualify the tool as a verification tool under the DO-178B?

• ○

  Is the installation procedure of the tool easy?

• ○

  Does the tool require a system with more than 4GB of RAM memory?

• ○

  Is the licensing scheme of the tool compatible with the confidentiality needs of the avionics company?
  
  

Select all that apply, then click Submit answer.

• ○

  The type of defect that caused the failure

• ○

  The actual and the expected result highlighting the failure

• ○

  The lifecycle phase in which the defect has been introduced

• ○

  What really caused the failure (actual cause)

• ○

  Steps to reproduce the failure, including screenshots, database dumps and logs where applicable
  
  

Select all that apply, then click Submit answer.

• ○

  The management asks the testers to be kept informed about the intensity, quality and results of testing.

• ○

  The testers’ recommendations to improve the system or its testability are adopted by the development team.

• ○

  The same regressions tests are manually executed by the same testers, for every product release, without regression test tools.

• ○

  The testers are assessed on whether and how often they detect important and critical failures.

• ○

  Test quality is measured by counting the number of customer/user reported problems.
  
  

Select an option, then click Submit answer.

• ○

  You should plan for lightweight exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects.

• ○

  You should plan for formal exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects.

• ○

  You should plan for formal exit-phase reviews at the end of each development phase and testing phase, and plan for a process of gathering information from testing to perform an analysis of the bugs found during testing to determine the people responsible for those bugs.

• ○

  You should plan for formal exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis of the bugs found during testing to determine the phase in which they have been introduced.
  
  

Select an option, then click Submit answer.

• ○

  Define very detailed mission statements, which allow testing work to be broken into sessions of up to 10 minutes duration in which testing is guided by these mission statements.

• ○

  Break the testing work in 30 to 120 minutes sessions and use properly defined mission statements consisting of two or three sentences to guide testing during these sessions.

• ○

  Define very generic charters to drive exploratory testing sessions of 2 days where testers are completely free to decide what to test.

• ○

  Exploratory testing should not be managed because such testing is inherently unmanageable and not measurable.
  
  

Select an option, then click Submit answer.

• ○

  Archive all the test results of the acceptance testing phase.

• ○

  Deliver a list of the open defects of a software product released into production to the service desk team.

• ○

  Participate in a meeting at the end of a project aimed at better managing the events and problems of future projects.

• ○

  Deliver an automated regression test suite, used during the system test phase of a software product released into production, to the team responsible for maintenance testing.
  
  

Select an option, then click Submit answer.

• ○

  Mature organizations address product quality risks associated to non-functional characteristics only during the system test phase.

• ○

  Mature organizations are aware that the contribution of testing to analysis of product quality risks is very important. The analysis should occur throughout the entire life cycle.

• ○

  Mature organizations don’t waste time identifying the sources of risks. They only focus on identifying product quality risks.

• ○

  Mature organizations are aware that risk management of product quality risks only occurs during testing.
  
  

Select an option, then click Submit answer.

• ○

  The chart indicates that you have plenty of problems left to find.

• ○

  The chart can be used to reveal test progress problems.

• ○

  The chart seems to indicate that the defect management process is not working well.

• ○

  The chart seems to indicate that the defect management process is working well.