ISTQB Ctal Tm 2012

Correct: has the input to occur, the correct expected result per the scenario, and relates to the risk item.
Incorrect: has the wrong expected result and so it incorrect.
Incorrect: might cover this risk item, but it is a negative test and also does not contain an expected result; it’s a good exploratory negative test for this risk item, though.
Incorrect: is a perfectly goo d positive logical test, but does not cover the risk item.

Correct: Both initial triage and assignment may decide to reject a defect (hence transition to REJECTED). If testing finds defect not fixed then it will move to REOPENED. Both initial triage and assignment may decide that a defect may be deferred (perhaps to a later release).

Incorrect: STATE X – RETESTED; STATE Y - NEW; STATE Z – BLOCKED No point retesting immediately after testing. NEW is often synonymous with OPEN.
If state Z was blocked, then you cannot exit this state.

Incorrect: STATE X – DUPLICATE; STATE Y - UNCONFIRMED; STATE Z – TERMINATED A duplicate defect would not require re-assignment. Unconfirmed as state Y does not work as you cannot leave this state. State Z could be terminated in some schemes.

Incorrect: STATE X – VERIFIED; STATE Y - REVIEW; STATE Z - FIXED Verified and tested are often synonymous – so both not needed. Review as state Y does not work as you cannot leave this state. State Z as fixed does not work – fixed is synonymous with resolved and you cannot get from state Z to ‘CLOSED’.

Correct: per syllabus section 1.3

Correct: it mentions three of the five main dimensions of test progress metrics.
Incorrect: Estimation of code coverage by measuring the number of executed tests combines wrong coverage to number of executed tests.
Incorrect: Combined usage of coverage, product, people, test and defect metrics includes people category, which is unlikely to be used for test progress monitoring; also, people and product are not listed in the five main dimensions of test progress metrics.
Incorrect: Combined usage of product , people and project metrics includes people category, which is unlikely to be used for test progress monitoring.

Correct: this metric will tell you automatically if you cover enough of the requirements to make it to the release deadline and if you have too much coverage on some areas.

Incorrect: Collect the number of test script executions per increment in a test management tool on its own doesn't tell anything, the tests could be all on same functional area. However, the measuring of test execution becomes easier with this.

Incorrect: Monitor the performance of the system, so you can tune its scalability concerns performance testing tools.

Incorrect: Measure the number of hours spent on test script development as an attribute of the test script this might help make collecting hours easier, but on its own doesn't help, time is mentioned as problem, so that might lead you to this option.

Correct: Root cause of the defects must be found
Incorrect: Postpone the review session and redefine the review with the objectives of the CD. All stakeholders must agree on the review objectives.
Incorrect: Proceed timely with the review session, with the role “scribe” assigned to the CD “punishment” don’t help, be constructive!
Incorrect: Cancel the review, write a report to upper management emphasizing the missing involvement of the CD accuses don’t help, be constructive!

Correct: You may tailor a set of templates from various sources, including the IEEE 829 standard. Agile lifecycles emphasize lightweight documentation.
Incorrect: You should follow the IEEE 829 standard, since you are following a process-compliant test strategy. the process being compliant with in this case is Agile methodology, not IEEE 829.
Incorrect: You should follow the IEEE 829 standard, because it was designed for use in any industry. IEEE 829 is documentation-heavy and thus incompatible with Agile philosophies on documentation and with reactive test strategies.
Incorrect: You may omit documentation of test work altogether, except for defect reports. even reactive test shave charters and even Agile lifecycles have acceptance criteria.

Correct: Coding skills are necessary for the actual scripting and design skills are very useful to ensure good design of the keyword-driven framework.

Incorrect: V,Y Neither of these can write code, which is necessary to write the scripts.

Incorrect: X,Z Neither of these can write code, which is necessary to write the scripts.

Incorrect: Y,Z Neither of these can write code, which is necessary to write the scripts.

Correct: Aligning tester bonuses with delivered quality can be demotivating as the testers have an indirect impact on delivered quality – and in this scenario the deliverable is not meeting customer expectations, so is probably perceived to be of low quality.

Incorrect: There appears to be mutual respect between the testing team members and the web developers. This is motivating behavior– from syllabus.

Incorrect: The testers have been given increased responsibility and are expected to manage their own time. This is motivating behavior– from syllabus.

Incorrect: Management are providing visible recognition for the work being done by the testers. This is motivating behavior– from syllabus.

Correct: Resignation of senior marketing staff prior to introduction of the service. While this is a significant project risk, it is not a test related project risk. What the test team needs from the marketing team—the requirements— are already complete.
Incorrect: Inability to provision a test environment by the planned test execution start date. problems with test environment readiness are classic test-related project risks.
Incorrect: Inability to locate sufficient skilled and certified testers, especially senior testers. problems with test staff availability and qualification are classic test-related project risks.
Incorrect: Insufficient resources to acquire suitable number of virtual users for load testing. problems with tool readiness are classic test-related project risks.

Correct: From syllabus.
Incorrect: ISTQB syllabi and glossary. Not a standard – does not provide guidance on test coverage criteria.
Incorrect: CMMI software process improvement framework. A generic process improvement model – does not provide guidance on test coverage criteria.
Incorrect: Prince 2 project management framework. A generic project management framework – does not provide guidance on test coverage criteria.

Correct: Web development and understanding of cloud computing relate to the technical elements of the project. Attention to detail is a personality trait needed in any review participant.
Having participated in reviews gives the individual knowledge of the review procedure. Financial applications manage balances, which is relevant to managing loyalty point balances.

Other answers are all incorrect because of one or more mismatches.

Correct: we are using the criteria to assess status and, based on that assessment, to decide future actions, which are actions that the syllabus says belong in a management review.
Incorrect: The meeting is an audit, because the project management team is checking compliance against defined criteria by checking evidence, while we are indeed checking against defined criteria, there is no independent evaluation of compliance (the checking is being done by the project team) and there's no indication that "evidence" is being checked.
Incorrect: The meeting is a management review, because the project management team is checking to ensure that progress is being made on the project, while the statement is in a sense true, it misses the element of decision-making by management peers, which is the key reason that this is a management review rather than an audit.
Incorrect: The meeting is an audit, because the project management team is going to issue a pass/fail assessment against the criteria, while a pass/fail assessment of the criteria might well occur, as with B, there is no independent evaluation of compliance.

Correct: Diplomacy and objectivity are important to build trust in the new outsourcing setting; reviews are constructive means to transfer knowledge of the internal team to the off-shore team.

Incorrect: Send detailed defect report s and defect rates to upper management to get more time for the internal test team to perform usability testing. Upper management won’t want to see detailed defect reports.

Incorrect: Schedule a video conference with the off-shore test team and upper management to find the root causes for not finding the defects. Upper management won’t want to be involved in the root cause investigation.

Incorrect: Send detailed defect report s and defect rates to the off-shore team and ask for the root causes for not finding the defects. Off-shore team alone won’t be effective to find the root causes

Correct: defect repair time may delay testing but do not require test effort.
Incorrect: Even mature test processes could last long, if effort is high.
Incorrect: Detailed test conditions demand effort.
Incorrect: High quality systems demand more testing effort.

Correct: it combines using more different dimensions of test progress monitoring and starts looking into the probably real reason of test coverage versus effort spent leading to remaining product risks.
Incorrect: Add more tests to better cover the functionality is all right but no analysis involved, shouldn't work on intuition only.
Incorrect: Derive risk and confidence status from tester opinions about developer capabilities focuses wrongly on capabilities.
Incorrect: Include confidence rating into measures is all right on its own but it doesn't utilize the risk information.

Correct: $5,000 – ($150 + $250) = $4,600.
Incorrect: The total cost of quality, including cost of prevention, for this dating application is $5,400 you can’t add averages to calculate a total, and besides you weren't given the cost of prevention.

Incorrect: cost of quality can be used to calculate the value of any quality-relate d activity, and is so used in industries around the world.
Incorrect: Each bug found by testing o offers the organization a potential $5,400 savings in cost of quality you have to subtract the average costs of detection and internal failure associated with testing to calculate the net potential savings, rather than adding those costs.

Correct: This is the correct answer concerning retirement, as there are lots of existing scripts, and regression test scripts are the ones used most often.

Incorrect The custom-built tool must be maintained and converted to the new environment activity is not necessary because the old tool will be retired.

Incorrect: The backup and restore functionalities of the custom-built tool must be maintained activity is not necessary because the old tool will be retired.

Incorrect: All test scripts of the custom-built tool must be converted to the new tool. Even if you would like, it is not realistic to convert all the scripts, if you can manage with just regression test scripts.

We do not want to leave all prioritization and effort allocation to individual testers, and also discovery of defects can only occur after testing (and so some prioritization and effort allocation) has already started.

Correct: From syllabus
Incorrect: Testing measures quality – it does not improve it (subsequent debugging would do).
Incorrect: There is no correlation between risk types (although these are both the same risk type) and functional/non-functional testing.
Incorrect: Project risks do help determine which test levels, but so do product risks.

Correct: This will show where defects are currently introduced, and so we can target these activities to prevent future defect introduction.

Incorrect: The phase of introduction may be useful, but the detection and removal info is not useful for reducing defect introduction.

Incorrect: The defect component information is used for defect clustering information to target components that need extra testing – but does not directly help prevent defects.

Incorrect: The defect removal efficiency information tells us how efficient we are at removing defects – it does not help with reducing the introduction of defects.

Correct: higher-risk tests precede lower-risk tests in risk-based testing strategies.
Correct: 02.019 covers a different requirement than 02.010.
Incorrect: the situation in option B, or perhaps simply blockage of tests, can explain running tests out of risk order.
Incorrect: while evaluating problems with test sequencing makes sense, there is no need to stop running tests while doing so.
Incorrect: finding defects is not the only objective of testing.

Correct: an onsite person will act as the channel of communication.
Incorrect: Division of the testing work based on qualifications there is no indication that any factor other than cost was used to select the outsource testing services firm.
Incorrect: Well-defined mission and tasks for on-site and offshore test teams there is no clear division of work between the teams
Incorrect: Establishment of trust across the project team members the decision about the use of this offshore team was imposed top-down, corroding trust from the very start.

Correct: PRAM, PRiSMa, FMEA, and FTA as these are four of the eight different techniques given in the syllabus.
Incorrect: Risk identification, risk assessment, risk mitigation, and risk management are the four activities in risk-based testing.
Incorrect: Expert interviews, independent assessments, use of risk templates, and project retrospectives are techniques for risk identification, which is only part of the analysis process.
Incorrect: Personnel and training issues among the business analysts, designers, and programmers is one of the factors influencing the likelihood of a risk item.

Correct: technical aspects covered by developers; functionality covered by internal testers and domain experts; internationalization covered by external experts.

Incorrect: Unit testing done by developers; component integration testing done by the independent internal test organization; system and user acceptance testing done by banking experts; internationalization testing outsourced to external test specialists. System testing done solely by banking experts: who tests web services?

Incorrect: Unit testing done by developers; system testing done by the independent internal test organization; user acceptance and internationalization testing done by banking experts supported by the independent internal test organization. No component integration testing; no internationalization test knowledge.

Incorrect: Unit and component integration testing done by developers; system and user acceptance testing and internationalization testing done by banking experts supported by the independent internal test organization. No internationalization test knowledge.

Correct: open source tools can be modified, and you have the capabilities, having earlier built custom tools, so you shouldn't care about adapting being hard.

Incorrect: The licensing terms need to be understood is a valid concern, as you need to adapt the tools and maybe give rights of your adaptations to open-source community, depending on licensing terms.

Incorrect: The telecom-standard compliance needs to be considered is a valid concern, as you need the telecom standard compliance.

Incorrect: Open-source tools have been created for a particular purpose is a valid concern, as you have your own specific purposes (which is why you originally had custom tools). Is the original purpose too far from what you need?

Because analytical risk based testing includes risk-based test prioritization, methodical testing follows a checklist (which in this example includes traversing links on a site), process-compliant testing can include Agile process compliance, and consultative testing involves being externally-directed.

All others are all incorrect because at least two of these examples are mismatched.

Correct: the test plan must be consistent with the larger project plan.
Incorrect: "The test manager should work with the project manager to develop the project schedule." is a true statement, but is about how testing affects a project management work product, not how a project management work product affects testing.
Incorrect: requirements are not a project management work product and, in addition, this statement is only true when following a requirements-based testing strategy.
Incorrect: "The test manager should work with the technical support manager during test closure." is a true statement as well, but not about project management affecting testing, but rather testing affecting technical support

Correct: the company’s hardware business unit changes hardware often (every six months).

Incorrect: The company has to follow telecom-standards would suggest using a ready-made tool, but standard-compliance could be met with custom-built tools also, although maybe with more effort.

Incorrect: The company has many developers capable of developing custom-built tool, so these skills should be utilized. This is a prerequisite, but not a reason.

Incorrect: The tool is easy to learn and use makes it attractive to keep the custom-made tool, but doesn't justify the great time spent to use and maintain the tool and the stem doesn't mention ease-of-use.

Correct: that is one of the test progress monitoring metrics. All are test metrics but used for a different thing.
Incorrect: Trends in the lag time from defect reporting to resolution is used to reward the developers refers to dangerous use of that metric.
Incorrect: Number of test conditions identified is used to monitor the quality of testing is really monitoring progress of test analysis.
Incorrect: Planned versus actual hours to develop testware is used to minimize regression testing is a metric to monitor progress of planning and control

Performance tests with maximum allowed response time 10 sec for up to 10,000 simultaneous requests of user story US 03-20 are missing

A test condition for user story US 02-20 is missing.

Correct: informal reviews are a lightweight approach that will achieve the benefits.
Incorrect: You should plan for inspections of requirements, design, and code reviews, management wants a lightweight process, and because the requirements (and possibly the design) are already complete.
Incorrect: You should plan for informal reviews of the quality risk analysis, tests, and test plan. is not as good an answer as because it specifically includes only test work products.
Incorrect: You should convince management that someone other than the test manager should plan the reviews, reviews can be planned and managed by various participants on a project, including the test manager.

Training the BAs is a cost of prevention because it helps write higher-quality requirements

Quality risk analysis is a detection cost because you’d incur this cost even if you found no defects

Any defect-related cost of quality incurred during testing and prior to release is a cost of internal failure, even avoidable costs

Customer complaints is a cost of external failure because these customer complaints result in decreased future sales.

Correct: this risk relates to the core functionality of the application.
Incorrect: tests with very high impact and higher likelihood should run before this test.
Incorrect: is not certainly true because we don’t know how this risk item relates to other risk items.
Incorrect: is not certainly true because we don’t know how effort allocation is determined based on combined impact and likelihood.

Correct: Since testing often accounts for a major part of the total project costs, more effective testing will lead to more effective projects. - syllabus sect. 5.2.

Correct: Test process improvement models help to reach a higher level of maturity and professionalism. - syllabus sect. 5.3.

Correct: users care about receiving the service they are paying for, at the agreed price; managers and stakeholders must care about all three types of tests, so that they have satisfied customers, a profitable company, and legal compliance; government agents care about compliance with the rules; and, married couples are not current stakeholders.
Incorrect: married customers are not current customers (unless they are cheating on their spouse) and thus shouldn't really care if invoicing is working correctly.
Incorrect: government employees wouldn't really care about how well the matching works, except for those employees who are users of the application (which has nothing to do with being an employee of a government agency).
Incorrect: the users really don’t have much concern about whether the company is paying the proper taxes, as long as the user is being charged properly.

Correct: The system has excessive downtime due to memory leaks. we are promising high reliability and reliability is a quality characteristic.
Correct: The loyalty points calculated are incorrect. calculating loyalty points is a function of the system and functional accuracy is a quality sub-characteristic.
Correct: Customers cannot enroll in company loyalty programs. enrolling in company loyalty programs is a function of the system and functional accuracy is a quality sub-characteristic.
Incorrect: The start-up runs out of money before testing starts is a project risk (and a very real one for any start-up).
Incorrect: Cloud computing resources are not available quickly enough to support project schedules is a project risk, and requires the candidate to make the subtle distinction between the immediate potential effects of the risk (widespread collateral damage to the project) from the various consequences should the risk become an outcome (which includes various quality-related problems).
Incorrect: Overly aggressive discounts result in a liquidity crisis for the company during the first year is a project risk, not a quality risk, and it’s also of vanishingly small likelihood given the amazing range of options available in the cloud computing retail market.

Incorrect: is definitely a risk, but it’s not related to the quality of the system, but rather due to the discounts being offered; specifically, it’s an operational risk that can arise after release.

Correct: it corresponds to a defect that turns out
Incorrect: Initial, in progress, confirmation test, closed, deferred it makes no sense to defer a defect that’s already fixed
Incorrect: Initial, in progress, returned, in progress, confirmation test confirmation test is not a terminal state
Incorrect: In progress, initial, confirmation test, closed a defect report can’t be in progress before it’s even reported.

Correct: From the syllabus.

Incorrect: Only some test planning can be delegated to both TAs and TTAs.

Incorrect: All non-functional testing does not have to follow functional testing (but it should be based on perceived risks).

Incorrect: Some non-functional risks may be mitigated early, but some may be mitigated later
in the life cycle.

We always want test effectiveness (e.g. ability to detect defects) to be high no matter what level of risk is being mitigated.

Correct: Align testing improvements with those of the company. TMMi supports CMMi, which is your company’s choice.

Incorrect: Reach Optimized level to help prevent defects. Based on scenario-information it is unlikely you are this high.

Incorrect: Move from Initial level to Managed level. Based on scenario-information it is unlikely you are this low.

Incorrect: Reach 85 percent of specific and generic goals. Is irrelevant detail.

Correct: The priority to fix the problem. The third party needs this information to aid their prioritization.

Correct: The test environment in which the defect was observed. The test environment information will help them determine the environment where the defect becomes apparent.

Correct: Steps to reproduce the failure, along with the actual and expected results. These steps (and actual results) will help them understand the defect and the expected results will confirm that the testers understood what was expected.

Incorrect: The project activity occurring when the problem was detected. The third party already knows that these defect reports are coming from dynamic system testing.

Incorrect: Phase of detection is already available (system test), and phase of removal (hopefully now) is not known.

Incorrect: It is not the testers’ responsibility to determine the location of the defect in the system.

Correct: Testers and developers work together fits ”test is behind schedule”.

Incorrect: A requirements-based testing strategy is OK but requirements are not mentioned in the scenario.

Incorrect: Testware design leads software design. Design problems not mentioned in scenario.

Incorrect: Defects are systematically analyzed is OK but already done, since defects are classified.

Defect detection percentage (DDP) of unit test could not be measured timely.
Number of test conditions identified related to test analysis progress.
Unit test time vs. integration test time could not be measured timely.

Correct: specifying detailed test conditions could act in place of a poor test basis and contribute to defect prevention.
Correct: questions at test design to refine coarse grained test conditions would be expensive to answer.
Incorrect: Detailed test conditions would be hard to maintain.
Incorrect: questions at test design to refine coarse grained test conditions could be answered by domain experts.
Incorrect: Management doesn't general require that level of detail.

Correct: [TPI Next book p. 50]

for a mature application, the main mission of testing is really building confidence that the application continues to work properly. Automated regression testing helps achieve that efficiently, so the test process improvement and the application are aligned. While the idea of automating the regression testing For this mature application is a good one, automation does not tend to find many defects. So, the mission statement is not aligned with the test process improvement, or with the real test needs of a mature application.

Correct: CTP uses metrics to benchmark organizations against industry averages.

Incorrect: The test team’s test process maturity level goes from 2 to 3 would apply to TMMi.

Incorrect: The test team’s test process maturity level goes from controlled to efficient would apply to TPI-Next.

Incorrect: The assessment is part of the scope of the CTP model, but it is not an objective (except maybe for the consultant doing it).

Correct: Performance. tests have to be conducted; system not stable before day 10.
Correct: To reduce blocking failures after unit test and to improve communication between developer and tester.
Correct: 30% of performance issues are reported in relationship to web services . These (or some of them) may be due to undefined SLA.
Incorrect: Performance. tests are OK, but the 30% issues will only be found on system level with real services used.
Incorrect: Unit testing is under the hood of development.
Incorrect: There is no integration test level.
Incorrect: TDD starts with unit test case design; in agile processes normally there are no detailed design specifications.

Correct: Dealing with project schedule problems and expectation issues from customers and management It can be seen from the figures that following the original plan will not meet the schedule, and that this expectation needs to be managed.

Correct: Persuading team members that they are valued and that their input is a vital contribution to the team effort If team members feel they are valued they are more likely to contribute more.

Correct: Assimilating new member s into the team quickly, while still providing adequate supervision and support As we are getting two new team members, and timescales are short, we need to assimilate them into the team as quickly as possible.

Incorrect: Ensuring no favoritism by treating all team members the same and sharing all t asks across the team Treating all team members the same and sharing all tasks across the team does not make best use of the disparate skills of the different team members.

Incorrect: Showing your commitment by working in the testing team, delegating the handling of external issues to a team member As the team leader you have different responsibilities (and presumably skills) than the team members, so it is better use of your time to manage and them to test.

Incorrect: Closely managing the test team, only assigning individuals new tasks when the y finish their last one. It is better practice to provide more autonomy to the testers and allow them to manage their time more efficiently.

Incorrect: Analyzing personality traits to identify new skills to be acquired to increase each individual's skills portfolio Although analyzing personality traits to identify new skills to be acquired is good practice, it is not the most useful skill to be applied over the next four weeks.