Free ATM – Advanced Test Manager Practice Test Question

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 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.

• ○

  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.

• ○

  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 an option, then click Submit answer.

• ○

  Include people with the adequate level of knowledge, both technical and procedural

• ○

  Include people who are detail-oriented and scrupulous at finding issues

• ○

  Include as many people as possible in order to have more viewpoints about possible problems on the item under review

• ○

  Include people able to contribute to a clear, thoughtful, constructive and objective discussion
  

Select an option, then click Submit answer.

• ○

  Test reporting activities can’t be influenced by the use of an iterative lifecycle model with short iterations

• ○

  Test reporting activities are not important for projects adopting an iterative lifecycle model with short iterations

• ○

  Test reporting activities are less important for projects adopting an iterative life cycle model with short iterations. They should be performed at the end of the last iteration

• ○

  Test reporting activities are still important with an iterative lifecycle. The reports can be used to conduct post-iteration review sessions before starting with the next iteration
  

Select an option, then click Submit answer.

• ○

  Alex

• ○

  Roberta

• ○

  John

• ○

  Mark
  

Select an option, then click Submit answer.

• ○

  Defined entry and exit criteria

• ○

  Checklists to be used by the reviewers

• ○

  Deliverables such as reports, evaluation sheets or other review summary sheets

• ○

  Metrics for reporting on the review effectiveness, efficiency, and progress
  

Select an option, then click Submit answer.

• ○

  Don’t prepare any test and just run the regression test suite to check that the new features don’t introduce regression

• ○

  Make reasonable assumptions about the missing details and design lightweight tests that can be easily updated during test execution

• ○

  Don’t design any test until the test execution starts, then communicate that test execution is blocked due to incomplete requirements

• ○

  Even if there are only few details missing, escalate the risk to the project manager without preparing any tests