ISTQB CTFL-Agile Tester ISTQB Cert Exam Example - OFFICIAL Exam

Question 1 K1 The Agile Manifesto has 4 statements of values. Match the Agile value on the left (1-4) with its traditional counterpart on the right (i-iv). 1) Customer collaboration over i) Processes and tools 2) Responding to change over ii) Following a plan 3) Individuals and interactions over iii) Contract negotiation 4) Working software over iv) Comprehensive documentation Answer Set: A. 1 - iii, 2 - iv, 3 - ii, 4 - i B. 1 - iii, 2 - ii, 3 - i, 4 - iv C. 1 - iv, 2 - ii, 3 - i, 4 - iii D. 1 - ii, 2 - iii, 3 - iv, 4 - i

Question 1 FA-1.1.1 (K1) Recall the basic concept of Agile software development based on the Agile Manifesto Justification: A. Incorrect -options 2, 3, & 4 are incorrect - see (B) for correct answer. B. Correct - The Manifesto consists of 4 key values: Individuals and Interactions over processes and tools; Working software over comprehensive documentation; Customer collaboration over contract negotiation; Responding to change over following a plan. C. Incorrect - 1 & 4 are incorrect - see (B) for correct answer. D. Incorrect - all options incorrect - see (B) for correct answer.

Question 10 K2 Which of the following items should NOT be raised during a retrospective meeting? Answer Set: A. There should be more emphasis on unit testing in the future, to improve overall quality. B. The build process is manual and takes too long. Research and implementation of an automated build framework should be done. C. Tester XYZ is struggling to find defects. Test design training is required for this resource. D. Automated regression test suites are taking too long to run. A review of the tests, to eliminate redundant or unnecessary tests, is required.

Question 10 FA-1.2.3 (K2) Understand how retrospectives can be used as a mechanism for process improvement in Agile projects Justification: A. Incorrect - This should be raised in order to help find defects earlier in the process. B. Incorrect -This should be raised as a process improvement. C. Correct - The retrospective meeting is not meant to single out individuals, but to focus on improvements of the process, and the team as a whole. D. Incorrect - This should be raised as a process improvement.

Question 11 K2 Which of the following is NOT a principle of continuous integration? Answer Set: A. Continuous integration helps to build changed software regularly, including testing and deploying, in an automated way. B. Continuous integration allows new builds to be available frequently to testers and stakeholders. C. Continuous integration helps to identify new integration defects early and makes the analysis of these defects easier. D. Continuous integration ensures that testing of builds is done manually, as this generates more reliable results than automated scripts.

Question 11 FA-1.2.4 (K2) Understand the use and purpose of continuous integration Justification: A. Incorrect - This is a principle of continuous integration; builds are done at least once per day with automatic deploy and execution of automated unit & integration tests. B. Incorrect - Continuous integration allows for constant availability of an executable software at any time and any place, for testing, demonstration, or education purposes. C. Incorrect - The Continuous Integration practice enables developers to integrate work constantly, and test constantly, so errors in code can be detected rapidly. D. Correct - Testing should be automated at the unit and integration level to allow for quick feedback on the quality of the build.

Question 12 K1 Which of the following activities would a tester do during release planning? Answer Set: A. Produce a list of acceptance tests for user stories B. Help break down user stories into smaller and more detailed tasks. C. Estimate testing tasks generated by new features planned for this iteration. D. Support the clarification of the user stories and ensure that they are testable

Question 12 FA-1.2.5 (K1) Know the differences between iteration and release planning, and how a tester adds value to each activity Justification: A. Incorrect - This is expected during iteration planning. B. Incorrect - This is expected during iteration planning. C. Incorrect - This is expected during iteration planning. D. Correct - This is expected during release planning.

Question 13 K1 What is the most appropriate explanation of a 'user story'? Answer Set: A. An artifact that the tester must review and sign off before testing can begin. B. An artifact used to detail only the functional requirements of the system. C. An artifact documented by business representatives to help developers and testers understand the system requirements. D. An artifact written collaboratively by developers, testers, and business representatives to capture requirements.

Question 13 Agile Extension-Term (K1) Justification: A. Incorrect - The tester participates in the creation of the user story. B. Incorrect - The user story should include both functional and non-functional requirements. C. Incorrect - The user story is written collaboratively by the developers, testers, and business representatives. D. Correct - In an Agile environment, user stories are written to capture requirements from the perspectives of developers, testers, and business representatives. The collaborative authorship of the user story can use techniques such as brainstorming and mind mapping.

Question 14 K2 Which of the following test activities is typically done during agile projects, but is not as common on traditional projects? Answer Set: A. Testers write detailed test plans so all team members can understand what will be tested during each iteration. B. Testers are heavily involved in the creation of automated test cases which are then used to verify the implementation of the requirements. C. Testers perform exploratory testing in order to find important defects quickly. D. Testers collaborate with developers to better understand what needs to be tested.

Question 14 FA-2.1.1 (K2) Describe the differences between testing activities in Agile projects and non-Agile projects Justification: A. Incorrect - Agile testing promotes lightweight documentation. B. Correct - Test automation at all levels occurs in many agile teams. As the developers focus on automating tests on unit level testers should focus on automating tests on integration, system, and acceptance level. In traditional projects it is not as common to have the same focus on automation. Sometimes automation is done once the system testing is completed in order to work with a stable system or just to automate regression tests for maintenance purposes after the system is deployed to production. C. Incorrect - Exploratory testing is likely to take place in any software development practice. D. Incorrect - Tester-developer collaboration is a good practice in all lifecycles.

Question 15 K2 Consider the following activities: i. Strict enforcement of system test level entry and exit criteria. ii. Collaboration between tester, developer, and business stakeholders to define acceptance criteria. iii. Functional verification testing of user stories developed in the previous iteration. Which of the following combination of these activities should occur in an agile project? Answer Set: A. ii only B. i and ii C. ii and iii D. iii only

Question 15 FA-2.1.2 (K2) Describe how development and testing activities are integrated in Agile projects Justification: A. Correct - These three perspectives (tester, developer and business representative) are important to define when a feature is done. B. Incorrect - Test level entry and exit criteria are more closely associated with traditional lifecycles. C. Incorrect - Features should be verified in the same iteration in which they are developed. D. Incorrect - Features should be verified in the same iteration in which they are developed.

Question 16 K2 Which TWO of the following statements are true on agile projects? Select TWO options. Answer Set: A. Testers should work closely with developers while retaining an objective outlook. B. Test managers do not exist in organizations doing agile development. C. There is no difference between what testers and developers do on agile projects. D. Developers should rely on testers to create the automated regression tests. E. A selection of users may perform beta testing on the product after the completion of a series of iterations.

Question 16 FA-2.1.3 (K2) Describe the role of independent testing in Agile projects Justification: A. Correct - This is one of the hallmarks of agile projects. B. Incorrect - Many agile project teams still have independent test teams with test managers C. Incorrect - Testing is still a specialized role in agile, when done properly. D. Incorrect - Developers and testers work collaboratively to develop and test a feature. E. Correct - Agile teams can employ various forms of acceptance testing.

Question 17 K2 Which of the following statements about independent testing on agile projects is FALSE? Answer Set: A. There can be a risk of losing test independence for organizations introducing agile. B. Independent testers will find more defects than developers regardless of test level. C. Independent testing can be introduced at the end of a sprint. D. The independent test team can be part of another team.

Question 17 FA-2.1.3 (K2) Describe the role of independent testing in Agile projects Justification: A. Incorrect - This is a true statement. This can happen when testers and developers work closely together. B. Correct -This is a false statement. Independent testers CAN find more defects than developers, but this is dependent on the level of testing being performed and also the expertise of the independent tester. C. Incorrect - This is a true statement. This is an option which preserves a level of independence where there are separate test and development teams and testers are assigned on-demand at the end of a sprint. D. Incorrect - This is a true statement. This option is satisfied when there are some specialized testers working on non-sprint or long term activities.

Question 18 K2 In an agile project, which of the following would best denote product quality at the end of iteration 6 of a new system release consisting of 8 iterations? Answer Set: A. No severity 1 or 2 defects were detected during system testing of iteration 6, which allowed the teams to move into iteration 7. B. The results of a customer beta test on the iteration 6 software release indicate that the system works correctly and that it has improved productivity. C. The agile team has been successfully tracking to estimates, with limited variance showing on the burndown charts for all iterations to date. D. All story cards in scope for each iteration, up to the current iteration, have been marked as "Done", but with some technical debt being incurred.

Question 18 FA-2.2.1 (K2) Describe the tools and techniques used to communicate the status of testing in an Agile project, including test progress and product quality Justification: A. Incorrect - This may be an indicator of quality, but it assumes that sufficient testing has been conducted to identify all possible defects. Also, it does not identify if the system is considered to be "working software" at this point. B. Correct - Positive customer feedback and working software are key indicators to product quality. C. Incorrect - This is a good indication of team velocity, but does not provide information on the quality of the product. D. Incorrect - This is also a good indication of team velocity, but again does not provide information on the quality of the product.

Question 19 K2 Which of the following is best at showing the team's progress against estimates? Answer Set: A. Burndown charts B. Automation logs C. The agile task board showing user story and task progress D. Defect tracking tools

Question 19 FA-2.2.1 (K2) Describe the tools and techniques used to communicate the status of testing in an Agile project, including test progress and product quality Justification: A. Correct - Burndown charts show the planned progress and release date together with the actual progress of the user stories. B. Incorrect - automation logs show tests that have passed and failed and is not linked to any form of estimates. C. Incorrect - While the agile task board shows progress, this information is then used in the burndown chart. But the task board showing the progress of the user stories and tasks do not have anything to do with estimates. D. Incorrect - The defect tracking tool can show progress of defect reports and can be used to establish the quality level of the product. But it does not relate to the team's progress against estimates.

Question 2 K1 Which of the following statements best reflects one of the values of the Agile Manifesto? Answer Set: A. Working software allows the customer to provide rapid feedback to the developer. B. Developers should use unit testing tools to support the testing process. C. Business representatives should provide a backlog of user stories and their estimates to the team. D. Adopting plans to change adds no real value to an agile project.

Question 2 FA-1.1.1 (K1) Recall the basic concept of Agile software development based on the Agile Manifesto Justification: A. Correct - From a customer perspective, working software is much more useful and valuable than overly detailed documentation, and it provides an opportunity to provide the development team rapid feedback. B. Incorrect - It is normal practice, especially in test driven development, but it is not one of the values in the agile Manifesto. C. Incorrect - The value is: customer collaboration over contract negotiation. D. Incorrect - The value is: responding to change over following a plan.

Question 20 K2 The business advises during iteration 5 planning that they require changes to the system delivered in iteration 3. Of the following activities, which would need to be done first to minimize the introduction of regression risk when this feature is changed? Answer Set: A. Review and update all manual and automated tests impacted by this change to meet the new acceptance criteria. B. Write new manual and automated tests for the feature and add them to the regression test suite. C. Automate all test cases from the previous iteration and add them to the automated regression test suite. D. Increase the amount of test automation around the system to include more detailed test conditions.

Question 20 FA-2.2.2 (K2) Describe the process of evolving tests across multiple iterations and explain why test automation is important to manage regression risk in Agile projects Justification: A. Correct - As this feature has previously been delivered, a review of all test assets is required, which should result in the updating of test cases to meet new acceptance criteria, to ensure false negatives (i.e. invalid failing tests) do not occur. This is the initial task to be performed before a decision about any other changes can be made. B. Incorrect - This would not be the initial task to perform, as the tester would not know what new tests would be required for these changes without reviewing the current tests first. There may not be a need to add new tests - updates to existing tests may suffice. C. Incorrect - While this is good practice, it does not address the specific regression risk identified in this scenario. D. Incorrect - Same as with choice B. Without reviewing the current tests for this feature, it is unknown if additional automation is required.

Question 21 K2 Which TWO of the following are reasons why automation is essential within agile projects? i. So that teams maintain or increase their velocity ii. To prevent the test team from becoming bored with manual, repetitive tasks iii. To retest all test cases from previous iterations iv. To eliminate regression in the product due to high code churn v. To ensure that code changes do not break the software build Answer Set: A. i and iv B. i and v C. iii and iv D. ii and v

Question 21 FA-2.2.2 (K2) Describe the process of evolving tests across multiple iterations, and explain why test automation is important to manage regression risk in Agile projects Justification: A. Incorrect. B. Correct. See below for detailed justification. C. Incorrect. D. Incorrect. i. This is true because agile expects and manages change and each iteration will require more and more regression testing. If automation was not used, then the team's velocity would be reduced. ii. This is false. This is not a reason to introduce automation on a project. iii. This is false. We cannot retest/rerun all the test cases from a previous iteration. There are many test cases produced, with most being through manual exploratory testing, and it would not be feasible to automate everything. iv. This is false. Automation will help avoid regression in the product due to the high number of changes. But it will not guarantee that defects have not been introduced. v. This is true. Automation tools are linked to continuous integration tools that will execute and will highlight instantaneously if the new code breaks the build.

Question 22 K2 In agile projects there is more need for testers to understand and develop test automation scripts than in traditional projects. Of the following, which are the TWO reasons why this is a necessary skill on agile projects? i. Requirements change daily and have to be regression tested. This rapid change requires automated tests because manual testing is too slow. ii. The tests should generate feedback on product quality as early as possible. So all acceptance tests should be executed in each iteration, ideally as modifications are made. In practice that can only be realized by automated tests. iii. Test-First and Continuous Integration Practice require that the regression test suite is executed whenever changed code is checked-in. In practice that can only be realized by automated tests. iv. Iterations or sprints are of fixed length. The team has to guarantee that all tests can be completely executed at the last day of each iteration/sprint. In practice, that can only be realized by automated tests. v. Agile projects rely on unit testing rather than on systems testing. Since unit tests cannot be executed manually, all tests have to be automated tests. Answer Set: A. i & iii B. ii & v C. iv & v D. ii and iii

Question 22 FA-2.3.1 (K2) Understand the skills (people, domain, and testing) of a tester in an Agile team Justification: A. Incorrect - see justification below. B. Incorrect - see justification below. C. Incorrect - see justification below. D. Correct - see justification below i. Incorrect - Agile projects embrace and expect change, however this does not mean it happens daily. ii. Correct- This is true, the earlier the agile team gets feedback on quality, the better. iii. Correct- Test first and continuous integration require tests to be automated and to provide feedback on build, as part of automated build process. iv. Incorrect - Testing should be done throughout each iteration, not only at the end. v. Incorrect - Agile projects require different levels of testing, such as unit, system, and acceptance testing.

Question 23 K2 Which tasks are typically expected of a tester on an agile project? i. decide on user acceptance ii. design, create and execute appropriate tests iii. schedule defect reports for analysis iv. automate and maintain tests v. improve program logic by pair programming Answer Set: A. i & iii B. ii & iii C. ii & iv D. ii & v

Question 23 FA-2.3.2 (K2) Understand the role of a tester within an Agile team Justification: A. Incorrect - see justification below. B. Incorrect - see justification below. C. Correct - see justification below. D. Incorrect - see justification below i. Incorrect - This task is a collaborative effort for the whole team. ii. Correct- This activity is expected of the agile tester. iii. Incorrect - In agile, defects are communicated regularly with stakeholders. iv. True - This activity is typical for an agile tester. v. Incorrect - Pair programming is typically done using two developers; testers are not expected to improve program logic although could review code for testability or maintainability.

Question 24 K2 Which of the following is NOT a typical task performed by the tester within an agile team? Answer Set: A. To automate tests and maintain them B. To mentor and coach other team members C. To produce and update burndown charts D. To participate in code analyzing activities

Question 24 FA-2.3.2 (K2) Understand the role of a tester within an Agile team Justification: A. Incorrect - This is true. Part of the tester's role is to produce automation scripts, run and maintain them. B. Incorrect - This is true. The tester should coach all other team members in any testing related aspect. C. Correct - This is false. It is the Scrum Master's role (or what the equivalent role is called in other agile methodologies) to produce and update the burndown chart from the information supplied by the rest of the team. D. Incorrect -Within agile, the tester will provide feedback on the product at all stages, which might include code analyzing activities.

Question 25 K1 The term "burndown" refers to which of the following? Answer Set: A. A chart showing which team members are working the most, and are likely to be under stress B. A chart showing the progress of each user story, and when they are likely to be completed C. A chart showing the amount of work left to be done, versus the time allocated for the iteration D. A chart showing defects that have been fixed, and when the remaining defects are likely to be fixed

Question 25 Agile Extension-Term (K1) Justification: A. Incorrect - This explanation probably refers to "burnout" rather than "burndown". B. Incorrect - This definition is describing the agile task board. C. Correct - The burndown chart shows progress of the user stories that are complete (done), and an estimate of the remaining time to complete the rest of the user stories in the sprint. D. Incorrect - Burndown charts do not have any reference to defects fixed or waiting to be fixed.

Question 26 K1 Which of the following statements about Test Driven Development (TDD) is FALSE? Answer Set: A. TDD is a "test first" approach to develop reusable automated tests. B. The TDD cycle is continuously used until the software product is released. C. TDD helps to document the code for future maintenance efforts. D. The result of TDD are test classes used by the developer to develop test cases

Question 26 FA-3.1.1 (K1) Recall the concepts of test-driven development, acceptance test-driven development and behavior-driven development Justification: A. Incorrect - Test-Driven Development (TDD) is a technique used to develop code guided by automated test cases. It is also known as test first programming, since tests are written before the code. The tests are automated and are used in continuous integration. B. Incorrect - The process for TDD is repeated for each small piece of code, running the previous tests as well as the added tests. C. Incorrect - The tests serve as a form of executable design specification for future maintenance efforts. D. Correct - This is true of BDD - not TDD.

Question 27 K1 What does the term 'Test Pyramid' refer to and illustrate situations for? Answer Set: A. The team's testing workload increases from sprint to sprint B. The backlog size, and thus the number of tests, decreases C. The number of automated unit tests is higher than the number of automated tests for higher test levels. D. The number of automated tests in place increases from sprint to sprint

Question 27 FA-3.1.2 (K1) Recall the concepts of the test pyramid Justification: A. Incorrect - The workload for each sprint has nothing to do with the Test Pyramid concept. B. Incorrect - The testing backlog and number of tests has nothing to do with the Test Pyramid concept. C. Correct - The test pyramid emphasizes having more tests at the lower levels and a decreasing number of tests at the higher levels. D. Incorrect - The number of automated tests has nothing to do with the Test Pyramid concept.

Question 28 K2 Which of the following demonstrates effective use of the testing quadrants? Answer Set: A. When communicating test ideas, the tester can refer to the matching test quadrant, so that the rest of the team will better understand the purpose of the test. B. The tester can use the types of tests described in the testing quadrants as a coverage metric,the more tests covered from each quadrant, the higher the test coverage. C. The team should pick a number of tests expected from each quadrant, and the tester should design and execute those tests to ensure all levels and types of tests have been executed. D. The tester can use the testing quadrants during risk analysis; with the lower level quadrants representing lower risk to customer.

Question 28 FA-3.1.3 (K2) Summarize the testing quadrants and their relationships with testing levels and testing types Justification: A. Correct - The testing quadrants can be used as an aid to describe the types of tests to all stakeholders. B. Incorrect - This is not a good metric since not all test levels/types are applicable for a given system. C. Incorrect - The number of tests from each quadrant is dependent on the system under test and will rarely be equal for all quadrants. In some situations, there may not be any tests for a quadrant. D. Incorrect - The testing quadrants have no correlation with risk level.

Question 29 K2 Given the following user stories: "As a bank teller, I can easily navigate through the system menu and links, and find the information I am looking for" "For all users, the system must display all queries in less than 2 seconds, 90% of the time" And the associated test cases: TC1: Login as bank teller. Enter customer ID. Verify that the customer transaction history is easy to find, and that navigating through the menus is intuitive. TC2: Login as bank teller: Enter customer Name. Verify that the customer accounts are easy to find and that navigating through the menus is intuitive. TC3: Simulate expected traffic on system and validate the time for customer transaction history to display is less than 2 seconds. Which TWO test quadrants would the above test cases be part of? Answer Set: A. Q1 unit level, technology facing & Q2 system level, business facing B. Q2 system level, business facing & Q3 system or user acceptance level, business facing C. Q3 system or user acceptance level, business facing & Q4 system or operation acceptance level, technology facing D. Q2 system level, business facing & Q4 system or operation acceptance level, technology facing

Question 29 FA-3.1.3 (K2) Summarize the testing quadrants and their relationships with testing levels and testing types Justification: A. Incorrect - see below. B. Incorrect - see below. C. Correct - see below. D. Incorrect - see below, Q1 - Incorrect - These test cases are not technology-facing component tests. Q2 - Incorrect - Usability and performance tests are not part of the 2nd quadrant. Q3 - Correct - Usability testing is part of the 3rd quadrant. Q4 - Correct - Performance testing is part of the 4th quadrant.

Question 3 K2 Which TWO activities below best represent responsibilities that are consistent with agile development's Whole Team approach? Select TWO options. Answer Set: A. Testers are responsible for developing unit tests which they pass on to the developers for testing B. Business representatives are expected to select the tools the team will use during the project C. Testers are expected to work with customer representatives to create acceptance tests D. The whole team, not just testers, has responsibility for the quality of the product E. Developers are expected to test non-functional requirements (performance, usability, security, etc.)

Question 3 FA-1.1.2 (K2) Understand the advantages of the whole-team approach Justification: A. Incorrect - This depends on the skillset of the team; developers may take on this task. B. Incorrect - The team will work together to select tools that will enable them to be collaborative & efficient. C. Correct - Testers support & collaborate with business representatives to help them create suitable acceptance tests. D. Correct - In agile projects, quality is the responsibility of the whole team. E. Incorrect - Developers

Question 30 K3 At the beginning of the 5th iteration of a project, a new requirement was introduced to support a new type of browser. The tester realizes that the existing test automation framework and scripts will not support the new type of browser. What is the best course of action for the tester on this team to take? Answer Set: A. The tester should notify the team that they are planning on working extra hours throughout the next 2 sprints in order to update the existing test automation framework and scripts to support the new type of browser so as not to disturb the existing sprint plan. B. The tester will notify the team of the issue. A risk analysis is done, and the team decides that regression testing must be performed on the new type of browser in addition to the other supported browsers. The tester will update the sprint plan by adding tasks to modify the framework and scripts to support the new type of browser. C. The tester does some research and concludes that the risk is low that any new defects would be introduced in the new type of browser that have not already been found in other supported browsers. The tester continues with the existing sprint plan and makes no changes to test automation framework or scripts. D. The tester will stop what they are doing, design specific tests for compatibility testing of the new type of browser, and communicate with the team that any other testing work for the sprint will have to be pushed to the next iteration.

Question 30 FA-3.1.4 (K3) For a given Agile project, practice the role of a tester in a Scrum team Justification: A. Incorrect - Modifying the test automation framework and scripts to support the new type of browser may not be worth the effort if the risk is low that new defects will be found. A risk analysis should be done including the whole team and a collaborative decision should be made. B. Correct - The decision to modify the test automation framework and scripts should be done collaboratively with the whole team. The tester is then responsible to make changes to the iteration plan as required. C. Incorrect - The tester must notify the team who will then together decide what to do with the issue. D. Incorrect - It is not up to the tester alone to determine scope of work. This issue will be addressed by creating a new user story or modifying an existing user story, and will be addressed by the entire team during sprint planning.

Question 31 K3 Given the following results from a product risk analysis that occurred at the beginning of an iteration: • User story 1 (Performance): likelihood: high, impact: high • User story 2 (Security): likelihood: high, impact: high • User story 3 (Functional): likelihood: medium,impact: high • User story 4 (Functional): likelihood: high, impact: medium • User story 5 (Compatibility): likelihood: low, impact:low • User story 6 (Recoverability): likelihood: low, impact: low Which TWO of the following describes best what the team should do with this information? Select TWO options. Answer Set: A. Move onto planning poker session to estimate effort for user stories, and determine what can be done in the current iteration, and what needs to be added to backlog. B. Remove user stories 5 and 6 from the current iteration and move to a later iteration. C. Because of the number of high likelihood, high impact risks slotted for this iteration, the team has no choice but to extend the timeframe of the iteration by 2 weeks. D. The team should collaborate on effective ways to mitigate the high likelihood, high impact risks. E. The team should plan to complete all items in the current sprint, but save the lower risk items for the end of the sprint, and only test these items if there is time.

Question 31 FA-3.2.1 (K3) Assess product quality risks within an Agile project Justification: A. Correct - The information from the risk analysis is used during poker planning sessions to determine priorities of items to be completed in the iteration. Only after the poker planning sessions, would items be added to the backlog if it is determined that not all items can be completed in the iteration. B. Incorrect - At this point, we do not know if we have time to complete all tasks in the iteration. Just because something is high risk does not mean it will take a lot of effort to complete. We would only know after poker planning sessions. C. Incorrect - The iteration length of times are not extended. After the poker planning session, some items may be moved to backlog if determined there is not enough time to complete. D. Correct - Risk mitigation can be done before test execution occurs to reduce the level of risk. E. Incorrect - A planning poker session should be held first to determine what can be accomplished in the given iteration. If it is determined that there is not enough time to complete all items, it is probable that the lower risk items will be added to the backlog for future sprints.

Question 32 K3 Given the following user story: "As the president, any data I upload should not be viewable by any other user of the system" During the first poker planning session, the following story points were given based on risk, effort, complexity, and proper extent of testing: Customers: 5 Developers: 5 Testers: 20 What is the best outcome following this planning session? Answer Set: A. Because the customer's and developer's size estimates match, the team can be confident that this estimate is good and should move onto the next user story. B. The team should hold a conversation to understand why the testers felt this user story was significantly more work. Another round of the planning poker session should occur following that discussion. C. Because the customer owns the system in the end, the customers' estimates should be taken as correct when there is a conflict. D. The poker planning sessions should continue until all estimated story points are an exact match between customers, developers, and testers.

Question 32 FA-3.2.2 (K3) Estimate testing effort based on iteration content and product quality risks Justification: A. Incorrect - The customers and developers may have overlooked the difficulty of the test technique needed to validate the user story. Discussions must be held, and the entire team should be in agreement of the estimate. B. Correct - Planning poker sessions should continue for the user story, until the entire team is satisfied with the estimated effort. C. Incorrect - The entire team must agree on the estimate for the user story. The customer alone does not understand the complexity of developing or testing the functionality. D. Incorrect - It is not necessary that they match, a rule could be made that the highest estimate is taken, or an average taken of all three estimates. This is up to the team to decide before the planning poker session.

Question 33 K3 An agile team is assigned to a project to update an existing medical device to newer technologies. Since the last release of the existing medical device, a new version of the medical device standard has been released. User access to the device is changing and will be documented in user stories. Based on this information, and in addition to the user stories, which of the following would best provide relevant information to support your testing activities? i. Updated version of standards document for medical system. ii. Existing defects or typical defect areas in existing system. iii. Obsolete user access test cases and results for existing application. iv. Performance metrics for existing application. v. Defects logged during other similar conversion projects for medical devices. Answer Set: A. i, ii, iii, iv B. ii, iv, v C. i, ii, v D. All of the above

Question 33 FA-3.3.1 (K3) Interpret relevant information to support testing activities Justification: A. Incorrect - see below B. Incorrect - see below C. Correct - see below. D. Incorrect - see below i. This is helpful since we know there is a new version of the standard; existing test cases will need to be modified or new ones will need to be added. ii. This is helpful during the risk analysis phase. iii. This information is not helpful, since user access is changing with the new release of the device and new user stories have been documented. iv. Because new technology is being introduced, baselines should be obtained using devices with similar technology or defined performance requirements for this type of technology. v. This is helpful during the risk analysis phase.

Question 34 K2 Which alternative is the BEST description of when to stop testing (release criteria) in an agile project? Answer Set: A. All test cases have been executed. B. The probability of remaining faults has been reduced to a level that can be accepted by thecustomer C. The achieved test coverage is considered enough. The coverage limit is justified by the complexity of the included functionality, its implementation, and the risks involved. D. The iteration/sprint is finished

Question 34 FA-3.3.2 (K2) Explain to business stakeholders how to define testable acceptance criteria Justification: A. Incorrect - Both test cases and test charters are used as a basis for what to test. The number of executed test cases does not give any information about what has been covered (The number of test charters do not give any valuable information about coverage, either). B. Incorrect - This statement in itself is insufficient. It needs to be backed up by supporting information regarding test coverage and risks involved C. Correct - The obtained test coverage with supporting information makes it the best choice, even if more information would be needed. This includes information about found defects, their severity of occurrence, and taxonomy (how many serious problems in each area). This information gives a more complete basis for a release decision. You would also need information regarding the evaluated characteristics and how they affect the total picture regarding the completion of the system, and the related testing. D. Incorrect - The finish of an iteration/sprint implies that you stop testing when there is no more time which is not the best criteria for when to stop testing

Question 35 K2 Which TWO of the following are examples of testable acceptance criteria for test related activities? Select TWO options. Answer Set: A. Structure based testing: White box testing in addition to black box testing is used. B. System testing: At least 80% of functional regression tests are automated. C. Security testing: A threat risk analysis scan is completed with no faults identified. D. Performance testing: The application is responding in a reasonable amount of time with 5000 users. E. Compatibility testing: The application is working on all major browsers.

Question 35 FA-3.3.2 (K2) Explain to business stakeholders how to define testable acceptance criteria Justification: A. Incorrect - not testable, there are no details on the type of white box testing or the coverage expected. B. Correct - this is testable. C. Correct - this is testable. D. Incorrect - not testable, we do not know what is a reasonable response time. E. Incorrect - not testable, need to specify which browsers. One could make assumptions on what the major browsers are.

Question 36 K3 Given the following User Story: "As a bank teller, I would like to be able to view all of my customer's bank transactions on the screen, so I can answer his/her questions". Which of the following can be considered as relevant acceptance test cases? i. Login as a bank teller, get the customer's account balance for all open accounts. ii. Login as a bank teller, enter a customer account ID, get his transactions history on the screen iii. Login as a bank teller, request customer account ID by using name abbreviations, and get his transaction history on the screen iv. Login as a bank teller, enter a customer IBAN (international bank account number), get his transaction history on the screen v. Login as a Bank Teller, enter a customer Account ID, get the Transactions history in less than 3 seconds on screen. Answer Set: A. i, ii, iv B. i, iii, iv C. ii, iv, v D. ii, iii, iv

Question 36 FA-3.3.3 (K3) Given a user story, write acceptance test-driven development test cases Justification: A. Incorrect - see justification below. B. Incorrect - see justification below. C. Incorrect - see justification below. D. Correct - see justification below. i. Incorrect - User story is specific to customers' transaction history. ii. Correct - This test is specific to a bank teller role and results in viewing customer's bank transactions. iii. Correct - This test is specific to a bank teller role and results in viewing customer's bank transactions. iv. Correct - This test is specific to a bank teller role and results in viewing customer's bank transactions. v. Incorrect - User story does not mention performance requirements.

Question 37 K3 Given the following user story: "An online application charges customers to ship purchased items, based on the following criteria: • Standard shipping costs for under 6 items • Shipping is $5 for 6-10 items. • Shipping is free for more than 10 items. Which of the following is the best black box test design technique for the user story? Answer Set: A. State Transition testing: Test the following states - browsing, logged in, selecting, purchasing, confirming, and exiting. B. Decision tables: Test the following conditions - User logged in; At least 1 item in cart; Purchase confirmed; Funding approved; with the resulting action of - Ship Item. C. Boundary Value Analysis: Test the following inputs - 0,5,6,10,11,max D. Use Case Testing: Actor=customer; Prerequisites=customer logs in, selects and purchases items; Postconditions= items are shipped.

Question 37 FA-3.3.4 (K3) For both functional and non-functional behavior, write test cases using black box test design techniques based on given user stories Justification: A. Incorrect - The focus of this user story is not on the state of the system; instead the expectation is to test shipping costs. B. Incorrect - The focus of this user story is not on whether the item is shipped as expected; the expectation is to test shipping costs. C. Correct - BVA is the best option when testing shipping costs. D. Incorrect - The focus of this user story is not on whether the item is shipped as expected, the expectation is to test shipping costs.

Question 38 K3 Your manager would like to introduce exploratory testing to your agile team. He has received the following suggestions on how to proceed from previous colleagues: i. User stories are assigned to testers who are completely new to the user story. There is allotted 120 minutes allocated to complete exploratory testing on the user story. Testers do not need to document tests, or test results, but do need to log defects if any are encountered. ii. User stories are assigned to testers who have already completed risk based testing on the same areas. There is allotted 120 minutes allocated to complete exploratory testing for this user story. The team expects at the end of the 120 minutes to have a list of test ideas, including data and actors, results and issues encountered, and list of defects to be logged in the defect management tool. iii. A user story is assigned to business representative. The business representative is told to use the system like the customer would on a day-to-day basis. If issues are encountered, the business representative is told to inform the tester, so that they can prioritize and log the defect. iv. A user story is assigned to a tester for exploratory testing. Tester is told to learn the functionality of the user story, to make sure the functionality is correct and to include negative testing. There is no set deadline for this exploratory testing to be complete; it depends on what is found by the tester. Documentation is not necessary, but defects need to be logged in defect tracking tool. Your manager presents you with his conclusions about how best to introduce exploratory testing to an agile team. Which one of your manager's conclusions is correct? Answer Set: A. Scenario i IS NOT the best way because: In exploratory testing, test design and test execution happen at the same time but are guided by a documented test charter that includes actors, test conditions, test data, etc. Test results are also documented and will guide the next test. B. Scenario ii IS the best way because: In this case, the testers have knowledge of the user story already, which will help them come up with test conditions and ideas. The team is using timeboxed exploratory test sessions. The team is expected to document test conditions, data, and user information, and to log results of the test. Issues are logged in a defect tracking tool just like any other test technique. C. Scenario iii IS NOT the best way because: This could be describing system acceptance testing, but not exploratory testing. D. Scenario iv IS NOT the best way because: documentation is necessary for exploratory testing, and testers must log test ideas and results of testing. The results of testing are used to guide future exploratory testing.

Question 38 FA-3.3.5 (K3) Perform exploratory testing to support the testing of an Agile project Justification: A. Correct - This is not a valid reason because exploratory testing cannot prevent defects from occurring due to the concurrent, reactionary nature of analysis, design and execution of the tests. B. Incorrect - Exploratory testing is known as an experienced based approach to testing, which will be as effective as the tester running the tests. The benefit of this approach is that the tests that will be designed and executed will influence the next set of tests that are designed and executed. C. Incorrect - Exploratory testing is not a technique but an approach to testing that can use other techniques such as pairwise, classification trees, boundary value analysis etc. D. Incorrect - One of the benefits of using exploratory testing is when there are requirements that are less than perfect, and within agile projects there is limited analysis, depth and detail of requirements.

Question 39 K1 Which of the following is one of the purposes of an Application Lifecycle Management (ALM) tool on an agile project? Answer Set: A. An ALM tool allows teams to build up a knowledge base on tools and techniques for development and testing activities B. An ALM tool provides quick response about the build quality and details about code changes C. An ALM tool provides visibility into the current state of the application, especially with distributed teams D. An ALM tool generates and loads large volumes and combinations of data to use for testing

Question 39 FA-3.4.1 (K1) Recall different tools available to testers according to their purpose and to activities in agile projects Justification: A. Incorrect - This would be one of the purposes of a wiki, not an ALM tool. B. Incorrect - This would be one of the purposes of a Continuous Integration (CI) tool, not an ALM tool. C. Correct - This is one of many purposes of an ALM tool, but using the tool allows more collaboration with distributed teams than physical task boards. D. Incorrect - This would be one of the purposes of a data generation and data load tool, not an ALM tool.

Question 4 K2 Which of the following is an advantage of having the whole team responsible for quality? Answer Set: A. Companies no longer need to recruit and train software testing specialists. B. Test automation tasks are now the responsibility of the development team instead of the test team. C. Role barriers are eliminated and team members contribute to project success based on their unique skills and perspectives. D. Project costs are lower because the need for a specialized test team is eliminated.

Question 4 FA-1.1.2 (K2) Understand the advantages of the whole-team approach Justification: A. Incorrect - Software testing skills should be transferred and extended to non-testing members of the team. B. Incorrect - This depends on the skillset of the team and who is available; some testers may have a development background. C. Correct - Enables a variety of skillsets to be leveraged as needed for the project. D. Incorrect - Specialized testers are still needed and are an important resource on agile projects.

Question 40 K1 Which of the following statements is FALSE with respect to exploratory testing? Answer Set: A. Exploratory testing encompasses concurrent learning, test design, and execution. B. Exploratory testing eliminates the need for testers to prepare test ideas prior to test execution. C. Best results are achieved when exploratory testing is combined with other test strategies. D. Exploratory testers need to have a solid understanding of the system under test.

Question 40 Agile Extension-Term (K1) Justification: A. Incorrect - This is true, see section 3.3.5 of syllabus. B. Correct - Test charters are created prior to execution which include test objectives and test ideas. C. Incorrect - This is true, see section 3.3.4 of syllabus. D. Incorrect - This is true; the tester needs good understanding of how the system is used and how to determine when it fails.

Question 5 K2 Which TWO of the following statements are true? 1) Early feedback gives the developers more time to develop new system features because they spend less time reworking features expected in a given iteration. 2) Early feedback enables agile teams to deliver features with the highest business value first, because the customer maintains focus on features with the highest system value. 3) Early feedback reduces costs because it decreases the amount of time needed for system testing. 4) Early feedback makes it more likely that the system built is what the customer wanted because they are given the opportunity to make changes throughout the iteration. Answer Set: A. 1 and 4 B. 2 and 3 C. 2 and 4 D. 1 and 3

Question 5 FA-1.1.3 (K2) Understand the benefits of early and frequent feedback Justification: A. Incorrect. B. Incorrect. C. Correct - See details below. D. Incorrect. 1) Incorrect - Developers only implement features that are requested by business and are part of an iteration. If they complete their tasks, they will help out with other tasks assigned to the iteration. 2) Correct - Frequent customer feedback maintains a focus on the features with the highest business value 3) Incorrect - There may be more testing required due to frequent changes. 4) Correct - Customers indicate if requirements are missed or misinterpreted, and modify functionality if they desire

Question 6 K2 Which of the following is a benefit of the agile process promoting early and frequent feedback? Answer Set: A. The total number of defects found during the project is much higher than on traditional software development projects such as waterfall. B. There is less rework because customers see the product regularly. C. It is easy to determine the developer who introduces the most defects when integrating code. D. There is enough time to complete all features scheduled for the given iteration.

Question 6 FA-1.1.3 (K2) Understand the benefits of early and frequent feedback Justification: A. Incorrect - The same number of defects may be found using any software development process. The benefit with agile is the ability to find and fix defects faster. B. Correct - Clarifying customer feature requests, early and regularly throughout development, making it more likely that key features will be available for customer use earlier and the product, will better reflect what the customer wants. C. Incorrect - Agile does not single out individuals; it is about the whole team. D. Incorrect - There may not be enough time to complete all features for a given iteration, but the agile process does allow the team to focus on those features that have the highest business value.

Question 7 K1 Match the following agile software development approaches on the top with their corresponding descriptions on the bottom. 1) Extreme Programming 2) Scrum 3) Kanban I. Embraces 5 values to guide development: Communication, Simplicity, Feedback, Courage, and Respect II. Divides the project into short iterations called sprints. III. Optimizes the 'flow' of work in a value-added chain. Answer Set: A. 1-i, 2-iii, 3-ii B. 1-i, 2-ii, 3-iii C. 1-ii, 2-i, 3-iii D. 1-iii, 2-ii, 3-i

Question 7 FA-1.2.1 (K1) Recall Agile software development approaches Justification: A. Incorrect - See B for correct mapping. B. Correct - Extreme Programming embraces 5 values to guide development: Communication, Simplicity, Feedback, Courage, and Respect. Scrum divides the project into short iterations called sprints. Kanban has no iterations or sprints; it is used to optimize continuous flow of tasks and minimize throughput time of each task. C. Incorrect - See B for correct mapping. D. Incorrect - See B for correct mapping.

Question 8 K3 During an iteration planning meeting, the team is sharing their thoughts about a user story. The product owner advises that the customer should have one screen to enter information. The developer explains that there are technical limitations for the feature, due to the amount of information needed to be captured on the screen. Another developer says that there are risks about performance as the information will be stored in an external offsite database. Which of the following would best represent a tester's contribution to this discussion? Answer Set: A. The tester advises that the screen for the user story needs to be a single page to reduce test automation effort. B. The tester advises that usability is more important than performance. C. The tester advises that performance acceptance criteria should standard maximum of 1 second for data storage. D. The tester advises that the user story needs acceptance criteria to be testable.

Question 8 FA-1.2.2 (K3) Write testable user stories in collaboration with developers and business representatives Justification: A. Incorrect - It is important to consider testability and automation, but designing the application based on limiting the testing effort may not result in a suitable solution for the end-user. B. Incorrect - The product owner prioritizes the various quality characteristics. C. Incorrect - The performance acceptance criteria would normally be determined by the product owner. D. Correct - The tester contributes by ensuring that the team creates acceptance criteria for the user story.

Question 9 K2 Which of the following BEST describes a tester participating in a retrospective meeting? Answer Set: A. As a tester participating in a retrospective meeting, I should bring in topics that are related to testing only. All other topics will be covered by different participants. B. As a tester, I participate in a retrospective meeting as an observer, ensuring that the meeting follows the retrospective rules and agile values. C. As a tester participating in a retrospective meeting, I should provide feedback and input on all activities conducted by the team during the sprint. D. As a tester, I should only attend and participate in a retrospective meeting if I have any feedback and input related to activities conducted by the team during the sprint.

Question 9 FA-1.2.3 (K2) Understand how retrospectives can be used as a mechanism for process improvement in Agile projects Justification: A. Incorrect - Testers should participate in all aspects of the retrospective meeting. B. Incorrect - Testers should participate in all aspects of the retrospective meeting. C. Correct - All team members, both testers and non-testers, can provide input on both testing and non-testing activities. D. Incorrect - Testers can learn valuable information from the retrospective meeting to apply in subsequent iterations