ISTQB Agile Tester Certification Dumps
ISTQB Agile Tester Certification Dumps
Dumps
Q 1. The Agile Manifesto has 4 statements of values. Match the agile value (1-4) with its traditional
counterpart (i-iv).
1) Customer collaboration over
2) Responding to change over
3) Individuals and interactions over
4) Working software over
i) Processes and tools
ii) Following a plan
iii) Contract negotiation
iv) Comprehensive documentation
Answer Choices:
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
Q 2. Which of the following statements best reflects one of the values of the Agile Manifesto?
Answer Choices:
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.
Q 3. Which TWO activities below best represent responsibilities that are consistent with agile
development’s Whole Team approach?
Select TWO options.
Answer Choices:
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.)
Q 4. Which of the following is an advantage of having the whole team responsible for quality?
Answer Choices:
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.
Q 6. Which of the following is a benefit of the agile process promoting early and frequent feedback?
Answer Choices:
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.
Q 7. 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 Choices:
A. 1-i, 2-iii, 3-ii
B. 1-i, 2-ii, 3-iii
C. 1-i, 2-ii, 3-iii
D. 1-iii, 2-ii, 3-i
Q 10. Which of the following items should NOT be raised during a retrospective meeting?
Answer Choices:
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.
Correct Answer and Explanation:
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.
Q 12. Which of the following activities would a tester do during release planning?
Answer Choices:
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
Q 14. Which of the following test activities is typically done during agile projects, but is not as
common on traditional projects?
Answer Choices:
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.
Q 16. Which TWO of the following statements are true on agile projects?
Select TWO options.
Answer Choices:
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.
Q 17. Which of the following statements about independent testing on agile projects is FALSE?
Answer Choices:
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.
Q 18. 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 Choices:
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.
Q 19. Which of the following is best at showing the team’s progress against estimates?
Answer Choices:
A. Burndown charts
B. Automation logs
C. The agile task board showing user story and task progress
D. Defect tracking tools
Q 20. 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 Choices:
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.
Q 21. 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 Choices:
A. i and iv
B. i and v
C. iii and iv
D. ii and v
Q 22. 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 Choices:
A. i & iii
B. ii & v
C. iv & v
D. ii and iii
Q 24. Which of the following is NOT a typical task performed by the tester within an agile team?
Answer Choices:
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
Q 26. Which of the following statements about Test Driven Development (TDD) is
FALSE?
Answer Choices:
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
Q 27. What does the term ‘Test Pyramid’ refer to and illustrate situations for?
Answer Choices:
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
Q 28. Which of the following demonstrates effective use of the testing quadrants?
Answer Choices:
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.
Q 30. 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 Choices:
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 has 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.
Q 31. 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 Choices:
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.
Q 32. 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 Choices:
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.
Q 33. 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 Choices:
A. i, ii, iii, iv
B. ii, iv, v
C. i, ii, v
D. All of the above
Correct Answer and Explanation:
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.
Q 34. Which alternative is the BEST description of when to stop testing (release criteria) in an agile
project?
Answer Choices:
A. All test cases have been executed.
B. The probability of remaining faults has been reduced to a level that can be accepted by the
customer
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
Q 35. Which TWO of the following are examples of testable acceptance criteria for test related
activities?
Select TWO options.
Answer Choices:
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.
Q 36. 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 Choices:
A. i, ii, iv
B. i, iii, iv
C. ii, iv, v
D. ii, iii, iv
Q 37. 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 Choices:
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.
Correct Answer and Explanation:
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.
Q 38. 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 Choices:
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.
Q 39. Which of the following is one of the purposes of an Application Lifecycle Management (ALM)
tool on an agile project?
Answer Choices:
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
Q 40. Which of the following statements is FALSE with respect to exploratory testing?
Answer Choices:
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.
Q41. Which of the following statements is FALSE with respect to exploratory testing?
Answers
(41-50)
Q. 61: (Level K2) Out of the following which can be used to take advantage of
the whole team approach in Agile development?
A. Daily stand-up meeting.
B. Continuous integration.
C. Test Driven Development.
D. Pairing.
Explanation in favor of the correct answer:
Option (A) is False – as the team works together to create user stories.
Option (B) is False – as this depends on the skillset of the team; developers
may take on the task of non-functional testing.
Option (C) is True – as testers collaborate with the team on all tasks.
Option (D) is True – as quality is everyone’s responsibility and all team
members should work together to ensure that the desired quality levels are
achieved.
Option (E) is False – as the team collaborates to prioritize and estimate the
user stories.
<<<<<< =================== >>>>>>
Q. 64: (Level K2) Who is responsible for the quality of the product in Agile
projects?
A. Testers as they are testing the product before it reaches the real
customer.
B. Developers as they are developing the product based on the
requirements.
C. Business Analyst as they are responsible for writing the acceptance
criteria for the product.
D. The whole team has responsibility for the quality of the product.
E. The product owner as they specify the customer requirements to the
team.
Explanation in favor of the correct answer:
Option (A) is False – As testers help the team in testing tasks but they are
not responsible for quality as in traditional project development methods
Option (B) is False – As developers develop the stories and help the team
in automation
Option (C) is False – As Business Analyst creates the acceptance criteria
with the help of the team
Option (D) is True – As in agile projects, quality is the responsibility of the
whole team
Option (E) is False – As the Product owner represents the business and
provides frequent feedback to the team
<<<<<< =================== >>>>>>
Q. 65: (Level K2) The statement – Agile development is very “people-
centered” relates to Out of the following which Agile Manifesto values?
A. Individuals and Interactions over processes and tools;
B. Working software over comprehensive documentation;
C. Customer collaboration over contract negotiation;
D. Responding to change over following a plan;
Q. 67: (Level K2) Out of the following which is an advantage of holding the
whole team responsible for the product quality?
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.
Option (C) is True – as every member of the team is fully accountable for
the success of the project
<<<<<< =================== >>>>>>
Q. 68: (Level K2) Out of the following which can be used to draw advantage
of early and frequent feedback in Agile projects?
A. Involving business representatives in team planning meeting.
B. Involving testers in non-testing tasks based on their skillsets.
C. Asking Developer to work on automation tasks.
D. Asking the customer to see the product regularly.
Option (A) is False – as the task is not related to receiving early and
frequent feedback.
Option (B) is False – as the task is not related to receiving early and
frequent feedback.
Option (C) is False – as the task is not related to receiving early and
frequent feedback.
Option (D) is True – as the customer checks the product early and regularly
there is less chance for requirement misunderstandings which is the main
benefit of early and frequent feedback.
<<<<<< =================== >>>>>>
Q. 69: (Level K2) Out of the following which is a benefit of early feedback in
agile projects?
A. It helps to manage the team better.
B. It helps the team to deliver better quality software to the customer.
C. Early feedback results in fewer changes to the software.
D. Early feedback reduces the cost of the overall development cycle
Explanation in favor of the correct answer:
Option (A) is True – as the capability of the team members is quite
transparent to everyone and it is easy to manage the team better.
Option (B) is False – as early feedback avoids misunderstandings in
requirements but not necessarily results in better quality of software.
Option (C) is False – as more changes may be coming up due to early
feedbacks.
Option (D) is False – as more testing may be required due to frequent
changes.
<<<<<< =================== >>>>>>
Q. 70: (Level K2) Out of the following which is NOT a benefit of early
feedback?
A. Avoiding requirements misunderstandings.
B. Clarifying customers requests, making them available for customer use
early.
C. Early discovery and resolution of bugs.
D. Early feedback reduces costs because it decreases the amount of time
needed for testing.
Explanation in favor of the correct answer:
Option (D) is True – as more testing might be required due to frequent
changes.
Q. 71: (Level K2) Which out of the following TWO statements are true?
1. Early feedback can only be achieved by Continuous Integration
2. Early and frequent feedback helps manage the team better since the
capability of the team is transparent to everyone.
3. Early and frequent feedback helps the team find the high severity bugs
early.
4. Early and frequent feedback enables the Agile team to build a product
which reflects what the customer wants.
A. 1 and 4
B. 2 and 3
C. 2 and 4
D. 1 and 3
Explanation in favor of the correct answer:
Statement (1) is False – as continuous integration is one way to provide a
quick feedback, but it is not the only way.
Statement (2) is True – as it is easy to check the work done in an iteration
and see how it can be improved.
Statement (3) is False – as bugs can be found early but not necessarily the
high severity defects.
Statement (4) is True – as customers indicate if requirements are not met
early, and can modify the functionality requirements if required.
<<<<<< =================== >>>>>>
Q. 72: (Level K2) Which out of the following TWO statements are true?
1. Early feedback helps the team focus on the features with the highest
value or associated risk so they are delivered to the customer first.
2. Early feedback reduces the time needed for system testing because the
quality problems are discovered and resolved early.
3. Early feedback helps in avoiding requirement misunderstanding because
the customer sees the product regularly
4. Early feedback gives the testers more time to work on the features in the
next iteration because they spend less time testing the features in the
current iteration.
A. 1 and 4
B. 2 and 3
C. 2 and 4
D. 1 and 3
Explanation in favor of the correct answer:
Statement – (1) is True – as frequent customer feedback maintains a
focus on the features with the highest business value or associated risk.
Statement – (2) is False – as more system testing might be required due to
frequent changes.
Statement – (3) is True – as the customer is checking the product early
and regularly there is less chance of requirement misunderstanding.
Statement – (4) is False – as testers will work on the features included in
the current iteration. If they complete their testing, they will extend their
help to the remaining team members.
<<<<<< =================== >>>>>>
Q. 73: (Level K2) Which out of the following TWO statements are true?
1. Early feedback results in in-consistent project momentum.
2. Early feedback ensures that the product better reflects what the
customer wants
3. Early feedback reduces the time needed for testing because there are no
requirement’s misunderstandings.
4. Early feedback helps to find quality problems early.
A. 1 and 4
B. 2 and 3
C. 2 and 4
D. 1 and 3
Explanation in favor of the correct answer:
Statement – (1) is False – as early feedback results in consistent project
momentum.
Statement – (2) is True – as clarifying customer feature requests and
making them available to the customer early will produce a better product
meeting the expectations of the customer.
Statement – (3) is False – as early feedback can result in more changes
and requiring more and more testing.
Statement – (4) is True – as early and frequent feedback results in quality
issues found early.
<<<<<< =================== >>>>>>
Q. 74: (Level K1) Out of the following which roles are NOT defined according
to the Scrum software development approach?
A. Scrum Master
B. Product Owner
C. Development Team
D. Testing Team
Explanation in favor of the correct answer:
Option (A) is False – as Scrum Master is a role defined in Scrum. It is the
Scrum Master’s responsibility to ensure that Scrum practices and rules are
implemented and followed and to resolve any violations, resource issues,
or other impediments that could prevent the team from following the
practices and rules.
Option (B) is False – as Product Owner role is defined in Scrum. The
Product Owner represents the customer and generates, maintains, and
prioritizes the product backlog.
Option (C) is False – as the development team is responsible for
developing and testing the product. The team is self-organized and is
cross-functional.
Option (D) is True – as there is no separate role defined for the Testing
team. The development team cover both developer and tester roles and are
responsible for development and testing of the product.
<<<<<< =================== >>>>>>
Q. 75: (Level K1) Match the following terms on the top with their
corresponding best agile software development on the bottom.
1. Pair Programming, Test-First Programming
2. Backlog, Sprints
3. Work-in-progress limit, Lead time
i. Kanban
ii. Extreme Programming (XP)
iii. Scrum
A. 1-i, 2-iii, 3-ii
B. 1-i, 2-ii, 3-iii
C. 1-ii, 2-iii, 3-i
D. 1-iii, 2-ii, 3-i
Explanation in favor of the correct answer:
Option (C) is True – as Pair Programming, Test First Programming are
primary practices for Extreme Programming; Backlog, Sprints are the
instruments & practices for scrum; Work-in-progress limit and lead time are
the instruments for Kanban;
<<<<<< =================== >>>>>>
Q. 76: (Level K1) Out of the following which is NOT related to the ‘Scrum’
software development approach?
A. Sprint
B. Definition of Done
C. Lead Time
D. Product Backlog
Explanation in favor of the correct answer:
Option (A) is False – as it is true that Scrum divides a project into iterations
(called sprints) of fixed length.
Option (B) is False – as it is true that Definition of Done is the appropriate
criteria for sprint completion decided by the scrum team.
Option (C) is True – as Lead time is used in Kanban to optimize the
continuous flow of tasks.
Option (D) is False – as it is true that the product owner manages a
prioritized list of planned product items (called the product backlog).
<<<<<< =================== >>>>>>
Q. 77: (Level K1) Out of the following which is NOT one of the values to guide
development in Extreme Programming?
A. Simplicity
B. Quality
C. Courage
D. Feedback
E. Communication
Explanation in favor of the correct answer:
Option (C) is True – as quality is not the value in Extreme Programming
development, five values to guide development are communication,
simplicity, feedback, courage, and respect.
<<<<<< =================== >>>>>>
Q. 78: (Level K1) Out of the following which is NOT related to a ‘User Story’?
A. Story Acceptance criteria.
B. Story point.
C. Story priority.
D. Story Entry criteria.
Explanation in favor of the correct answer:
Option (A) is False – as this is related to the user story, Story Acceptance
criteria are collaboration defined by business representatives, developers,
and testers for each user story.
Option (B) is False – as this is related to the user story, a Story point is
assigned to each user story In the poker planning session.
Option (C) is False – as this is related to the user story, each user story is
assigned a priority by the business users during release planning.
Option (D) is True – as there are no Story Entry criteria.
<<<<<< =================== >>>>>>
Q. 79: (Level K1) Who is responsible for writing the ‘user story’ in Agile
projects?
A. It is the tester’s responsibility to write the user stories.
B. It is the scrum master’s responsibility to write the user stories for the
team.
C. It is the product owner’s responsibility to write the user stories for the
team.
D. User stories are written collaboratively by developers, testers, and
business representatives.
Explanation in favor of the correct answer:
Option (D) is True – as in the 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 like brainstorming and mind mapping.
<<<<<< =================== >>>>>>
Q. 80: (Level 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.
Out of the following which would best represent a tester’s contribution to this
discussion?
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 secondary data storage.
D. The tester advises that the user story needs acceptance criteria to be
testable.
Explanation in favor of the correct answer:
Option (D) is True – as it is essential to define an acceptance criterion
against which the application must be tested.
Q. 81: (Level K3) During an iteration planning meeting, the team is sharing
their thoughts about a user story. The tester has asked the following to the
product owner to add more clarity to the business value of the feature. Out of
the following which questions don’t add any value to the discussion?
A. The tester advises that the non-functional characteristics should be
defined for the user story.
B. The tester advises that the user story needs acceptance criteria that is
testable.
C. The tester asking open-ended questions regarding the missing details.
D. The tester advises that usability is more important than performance.
Explanation in favor of the correct answer:
Option (A)
is False – as this is important to the discussion. The tester contributes by
ensuring that the user story contains all non-functional requirements
details.Option (B) is False – as this is important to the discussion. The
tester contributes by ensuring that the team creates acceptance criteria for
the user story.
Option (C) is False – as this adds value to the discussion. It is the
responsibility of the tester to ask all questions about the missing
functionality which may result in the complexities of the product being
discussed, which could have been skipped by the team earlier.
Option (D) is True – as this is not adding any value to the discussion, the
reason being the quality characteristics are prioritized by the product
owner.
<<<<<< =================== >>>>>>
Q. 82: (Level K3) In an iteration planning meeting, the team is discussing a
user story for the new interface which will be integrated to external
applications in later iterations. After the discussion, the developers confirmed
that they have enough information to start with their development work. The
tester is not clear about some of the functionality which may be required for
integration testing later.
What should the tester do in this situation?
A. As the Integration testing will be done later, the tester can confirm the
functionality with the business representatives later.
B. The tester can collaborate with the developers to find out about the
missing functionality once the coding is finished.
C. The tester should ask open-ended questions to business representatives
to confirm the acceptance criteria and the missing functionality as it may
impact the testing.
D. The tester should not worry about the missing details as it is the team
responsible to provide all the details to the tester.
Explanation in favor of the correct answer:
Option (A) is False – as the tester should confirm the functionality In the
planning meeting, not later.
Option (B) is False – as the tester should ask questions to confirm the
functionality In the planning meeting.
Option (C) is True – as it is the responsibility of the tester to ask all
questions about the missing functionality which may result in the
complexities of the product being discussed, which could have been
skipped by the team earlier.
Option (D) is False – as the tester should make sure that all information is
available for testing the story.
<<<<<< =================== >>>>>>
Q. 83: (Level K3) In an iteration planning meeting, the team is discussing a
user story. The product owner advises that sensitive customer data is
captured as part of the story and should be encrypted. The developer explains
that the encryption could result in an increase in development time. Out of the
following which would best represent a tester’s contribution to this
discussion?
A. The tester advises that encryption will increase the testing effort as
there is more development required.
B. The tester advises that the priority of the story should be increased.
C. The tester advises that more performance testing will be required for the
user story.
D. The tester advises that the user story needs testable acceptance criteria
for the encryption functionality.
Explanation in favor of the correct answer:
Option (A) is False – as it is not necessary that the increase in development
effort will increase the testing effort.
Option (B) is False – as the product owner will prioritize the story, the tester
alone doesn’t decide that.
Option (C) is False – as changes to performance testing requirements will
be decided by the team, not by the tester alone.
Option (D) is True – as the tester should ensure that there is testable
acceptance criteria for all of the functions of the user story.
<<<<<< =================== >>>>>>
Q. 84: (Level K2) Out of the following which BEST describes a tester
participating in a retrospective meeting?
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 in 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 in the sprint.
Explanation in favor of the correct answer:
Tester participates the retrospective meeting not as an observer but he/she
remains the ears and eyes of the entire team in the sprint and remains
responsible for providing inputs to the team and feedback on all activities.
<<<<<< =================== >>>>>>
Q. 85: (Level K2) Out of the following which demonstrates effective use of the
testing quadrant?
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 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 a lower risk to the customer.
Explanation in favor of the correct answer:
It is the responsibility of the tester to select tests from a testing quadrant
and communicate with the team with clear objective of doing particular
tests.
<<<<<< =================== >>>>>>
Q. 86: (Level K2) One of the Agile teams are using the “Start, Stop, Continue”
exercise for their iteration retrospective.
Out of the following which one is from the “Stop” list?
A. Communicating better with each other.
B. Accepting the story with incomplete requirements.
C. Increase the coverage of Automation tests.
D. Improve the performance of the test environment.
Explanation in favor of the correct answer:
Option (A) is False – as it is from the “continue” list
Option (B) is True – as it is from the “stop” list. The team should stop
accepting the stories without complete requirements.
Option (C) is False – as it is from the “start” list
Option (D) is False – as it is from the “start” list
<<<<<< =================== >>>>>>
Q. 87: (Level K2) Out of the following which could be raised in the
retrospective meeting?
i. Frequent environment related issues are slowing down testing. A root
cause analysis of the environment issues is required.
ii. A new tool is needed for the team to better manage user stories.
iii. Automation coverage of unit tests should be increased to improve
overall quality.
iv. The team should plan for some social activity after the end of each
iteration.
A. i, ii, iii
B. i & iii
C. i, ii, iv
D. i, ii, iii, iv
Explanation in favor of the correct answer:
Statement (i) is True – as it could be raised as a process improvement.
Statement (ii) is True – as it could be raised as a process improvement,
this could improve the efficiency of the team.
Statement (iii) is True – as it could be raised as a process improvement.
Statement (iv) is True – as it could be raised; team activities can result in
better communication and team efficiency.
<<<<<< =================== >>>>>>
Q. 88: (Level K2) Out of the following which items should NOT be raised
during a retrospective meeting?
A. Test data creation taking a long time. There should be an automated
process to create test data.
B. Developers not finishing the development activities on time.
C. The percentage of automation tests need to be increased to reduce
regression risks.
D. The test environment is slow and frequently unavailable for testing.
Explanation in favor of the correct answer:
Option (A) is False – as this should be raised as a process improvement.
Option (B) is True – as the retrospective meeting is not meant to point
fingers at individuals or groups.
Option (C) is False – as this should be raised as a process improvement.
Option (D) is False – as this should be raised as a process problem and
bottleneck.
<<<<<< =================== >>>>>>
Q. 89: (Level K2) Out of the following which BEST describes a tester’s
contribution in a retrospective meeting?
A. As a tester participating in a retrospective meeting, I should only be
concerned about the test-related improvement decisions focused on test
effectiveness
B. As a tester, I should I should give feedback only on the automation tasks
so that I can improve test effectiveness
C. As a tester, I should provide feedback on all activities conducted by the
agile team during all the completed sprints.
D. As a tester, I should give feedback only on the development task so that I
can improve test effectiveness
Q. 101: (Level K2) Which out of the following is the purpose of hardening or
stabilization iterations in Agile projects?
A. It is used to resolve any lingering defects and other forms of technical
debts.
B. It is used for customer testing so the team can get the feedback on
product quality.
C. It is used to finish any pending automation tasks to achieve desired test
coverage. D. It is used for the team to work on process improvement
activities.
Explanation in favor of the correct answer:
Option (A) is True – as the bugs creeping out of previous iterations are a
form of Technical Debt. Hardening or stabilization iterations occur
periodically
to resolve technical debt in Agile development.Option (B) is False – as the
purpose of hardening or stabilization iterations is not for customer testing.
Option (C) is False – as the purpose of hardening or stabilization iterations
is not to catch up on automation tasks.
Option (D) is False – as the process improvement activities happen in
parallel with iteration activities.
<<<<<< =================== >>>>>>
Q. 102: (Level K2) Out of the following which test activities is typically done
during agile projects, but is not as common on traditional projects?
A. Testers prepare detailed test strategy to address all testing activities
during each iteration.
B. Testers spend a lot of time creating, executing and maintaining
automated tests and results.
C. Testers use defect based techniques to find defects.
D. Testers used risk-based testing as one of the test strategies.
Explanation in favor of the correct answer:
Option (A) is False – as lightweight documentation is favored in Agile
projects.
Option (B) is True – as test automation occurs at all levels in most agile
teams. In Agile projects testers focus on automating, executing and
maintaining tests on integration, system, and acceptance level. In
traditional projects, testers do not have the same focus on automation.
Option (C) is False – as defect based techniques such as software attacks
and error guessing are used in traditional projects also.
Option (D) is False – as risk-based testing techniques are used in
traditional projects also.
<<<<<< =================== >>>>>>
Q. 103: (Level K2) Which out of the following TWO statements are true on
agile projects?
Select TWO options.
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.
Explanation in favor of the correct answer:
The basic hypothesis of agile projects is a joint collaboration between
testers, developers, and business stakeholders being a homogeneous
cross-functional team operating for a common goal.
<<<<<< =================== >>>>>>
Q. 104: (Level K2) Consider the following work products used by Agile team
for development and testing activities:
i. Quality risk catalogs.
ii. Test Results log.
iii. User stories.
iv. Automated unit tests.
Which out of the above are Test work products?
A. i and ii
B. ii only
C. i and iii
D. All of the above.
Explanation in favor of the correct answer:
Statement (i) is True – as it is one of the Test work products.
Statement (ii) is True – as it is one of the Test work products.
Statement (iii) is False – as it is one of the business-oriented work
products, not a Test work product.
Statement (iv) is False – as these are the developer work products, not a
Test Work product.
<<<<<< =================== >>>>>>
Q. 105: (Level K2) Out of the following which combination of activities should
occur in an Agile project?
i. Functional verification testing of user stories developed in the previous
iteration.
ii. Tester, developer, and business representative working collaboratively to
determine whether the feature is fit for use.
iii. Re-running the automated unit tests and feature verification tests from
the current iteration and previous iteration.
iv. System test level entry and exit criteria.
A. ii and iv
B. i and ii
C. ii and iii
D. ii only
Explanation in favor of the correct answer:
Statement (i) is False – as features should be verified in the same iteration
in which they are developed.
Statement (ii) is True – as this is required in an Agile project as part of
feature validation testing.
Statement (iii) is True – as this is required in an Agile project as part of
regression testing which is a parallel process throughout the iteration.
Statement (iv) is False – as this is not required in Agile project. Test level
entry and exit criteria are more closely associated with sequential lifecycle
models.
<<<<<< =================== >>>>>>
Q. 106: (Level K2) Which out of the following TWO statements are true on
Agile projects?
A. Feature verification testing, which is often automated, may be done by
developers or testers.
B. Regression testing can be done by the business users either at the close
of each iteration, after the completion of each iteration, or after a series of
iterations.
C. Feature validation testing is usually manual and can involve developers,
testers, and business stakeholders working collaboratively
D. Acceptance testing can be done by developers, testers, and business
stakeholders working collaboratively
Explanation in favor of the correct answer:
Option (A) is True – as feature verification testing involves testing against
the user story’s acceptance criteria and is done by developers or testers.
Option (B) is False – as regression testing should be done by the tester, not
the business user.
Option (C) is True – as feature validation testing involves developers,
testers, and business stakeholders working collaboratively to determine
whether the feature is fit for use.
Option (D) is False – as acceptance testing is done by the client.
<<<<<< =================== >>>>>>
Q.107: (Level 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.
Out of the following which combination of these activities should occur in an
Agile project?
A. ii only
B. i and ii
C. ii and iii
D. iii only
Explanation in favor of the correct answer:
The basic hypothesis of agile projects is a joint collaboration between
testers, developers, and business stakeholders being a homogeneous
cross-functional team defining and operating on common acceptance
criteria.
<<<<<< =================== >>>>>>
Q.108: (Level K2) Out of the following which statements about independent
testing on agile projects is FALSE?
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
the 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.
Explanation in favor of the correct answer:
It is a misconception that Independent testers are more efficient than
developers.
<<<<<< =================== >>>>>>
Q. 109: (Level K2) Out of the following which testing tasks should NOT be
taken by the independent testing team on Agile projects?
A. System Integration testing.
B. Test data creation.
C. Non Functional testing
D. User story acceptance testing.
Explanation in favor of the correct answer:
Option (A) is False – as Independent testing team can work on the test
levels like system integration testing that might not fit well within a sprint.
Option (B) is False – as Independent testing team can work on test data
creation which is an iteration-independent activity.
Option (C) is False – as Independent testing team can work on non-
functional testing which is an iteration-independent activity.
Option (D) is True – as user story acceptance testing involves working
closely with developers and other team members so there is a chance to
lose test independence.
<<<<<< =================== >>>>>>
Q. 110: (Level K2) Which out of the following TWO statements are true for
independent test teams on agile projects?
1. Independent test Teams can be used for creating and supporting test
environments and data.
2. Independent testers can work on all the iteration testing activities.
3. Independent test teams can work as ‘on demand’ testers In the final days
of each sprint.
4. Independent testers can work on all the iteration automation activities.
A. 1 and 4
B. 1 and 2
C. 2 and 4
D. 1 and 3
Explanation in favor of the correct answer:
Statement (1) is True – as independent test teams can work on the
iteration-independent activities like creating and supporting test
environments and data
Statement (2) is False – reason being, if the team will work on the iteration
testing activities with the Agile team, then there is a chance to lose test
independence.
Statement (3) is True – as independent test teams can provide an
objective, unbiased evaluation of the software at the end of a sprint.
Statement (4) is False – reason being, if the team will work on the
automation testing activities with the developers, then there is a chance to
lose test independence.
Q. 111: (Level K2) Which out of the following TWO testing tasks can be taken by the
independent testing team on agile projects?
A. Non Functional testing.
B. Story level testing activities.
C. System Integration testing.
D. Story level automation activities.
Explanation in favor of the correct answer:
Option (A) is True – as an independent testing team can work on non-
functional testing which is an iteration-independent activity.
Option (B) is False – as story level testing involves working closely with the
developer so there is a chance to lose test independence.
Option (C) is True – as an independent testing team can work on the test
levels like system integration testing that might not fit well within a sprint.
Option (D) is False – as automation testing activities involve working
closely with the developer so there is a chance to lose test independence.
<<<<<< =================== >>>>>>
Q. 112: (Level K2) The Test manager wants to introduce Independent testing for one of
the Agile teams. Out of the following which is a good approach?
A. Engage the independent test team in iteration planning activities.
B. Engage the independent test team In the release planning to understand
the risk.
C. Engage the independent team carrying out test levels that might not fit
well within a sprint.
D. Engage the independent test team for the automation tasks in the
sprints.
Explanation in favor of the correct answer:
Option (A) is False – as testers working on the iteration should be engaged
in iteration related activities, not the independent test team.
Option (B) is False – as testers working on the iteration should be engaged
in release planning, not the independent test team.
Option (C) is True – as an independent testing team can carry out test
levels e.g. system integration testing, that might not fit well within a sprint.
Option (D) is False – as developers and testers work collaboratively to do
the automation task in the sprints
<<<<<< =================== >>>>>>
Q. 113: (Level K2) Out of the following which is an example of an independent test team
in Agile project?
A. On-demand Testers working In the final days of each sprint.
B. Testers implementing and updating test strategy.
C. Testers working on iteration automation activities.
D. Testers working with the team to write the user story.
Explanation in favor of the correct answer:
Option (A) is True – as on-demand testers working on final days of each
sprint can provide an objective, unbiased evaluation of the software.
Option (B) is False – as testers working on the test strategy is not an
example of an independent test team as a lot of collaboration is required
with the team for this task.
Option (C) is False – as testers working on iteration automation activities is
not an example of an independent test team as a lot of collaboration is
required with the team for this task.
Option (D) is False – as testers working on user stories is not an example
of an independent test team as a lot of collaboration is required with the
team for this task.
<<<<<< =================== >>>>>>
Q. 114: (Level K2) Out of the following which statements about Independent testing on
Agile projects is False?
A. Independent testing can be introduced at the start of a sprint.
B. An Independent test team can be part of another team.
C. There is a risk of losing test independence in Agile teams.
D. An Independent test team can carry out test levels that might not fit
within a sprint.
Explanation in favor of the correct answer:
Option (A) is correct – as it is false to say that in the start of iterations there
is more of a need for testers to work closely with developers; so there is a
chance to lose test independence.
Option (B) is incorrect – as it is true that this option is satisfied when there
are some specialized testers working on iteration independent or long-term
activities like developing an automated test tool or non-functional testing
etc.
Option (C) is incorrect – as it is true that this can happen when testers work
closely with developers.
Option (D) is incorrect – as it is true that independent testing team can
carry out test levels e.g. system integration testing, that might not fit well
within a sprint
<<<<<< =================== >>>>>>
Q. 115: (Level K2) Out of the following which is best at showing the team’s progress
against estimates?
A. Burndown charts.
B. Automation logs.
C. The agile task board showing user story and task progress.
D. Defect tracking tools.
Explanation in favor of the correct answer:
As per the definition of Burndown chart, it is a graphical representation of
work left to do versus time. That is, it is a run chart of outstanding work by
a team working on agile projects.
<<<<<< =================== >>>>>>
Q. 116: (Level K1) The term “Agile task board” relates to Out of the following which?
A. A chart showing the progress of each user story with their current
status.
B. A chart showing the sum of estimates of the work delivered across
iterations.
C. A chart showing the number of defects discovered during a given period.
D. A chart showing the amount of work left to be done, versus the time
allocated for the iteration
Explanation in favor of the correct answer:
Option (A) is True- as agile task boards are used to provide an instant,
detailed visual representation of the user stories and the whole team’s
current status.
Option (B) is False- as this is a velocity chart, not the Agile task board.
Option (C) is False- as this is a defect discover rate chart, not the Agile task
board.
Option (D) is False- as this is a burn-down chart, not the Agile task board.
<<<<<< =================== >>>>>>
Q. 117: (Level K1) Out of the following which is NOT used as Agile metric?
A. Burndown chart.
B. Velocity Chart.
C. Code Churn chart.
D. Daily Status report.
Explanation in favor of the correct answer:
Option (A) is incorrect – as it is true that Burndown chart is one of the Agile
metrics. It shows the amount of work left to be done, versus the time
allocated for the iteration.
Option (B) is incorrect – as it is true that Velocity chart is one of the Agile
metrics. It shows the sum of the estimates of the work delivered across
iterations. This may be used while selecting the stories for the next
iteration.
Option (C) is incorrect – as it is true that Code Churn is one of the Agile
metrics. It shows the number of defects discovered during a given period.
This may be used as criteria for stopping the testing.
Option (D) is correct – as it is false to say that daily status is not one of the
Agile metrics. The team shares the status in the daily stand-up meetings.
<<<<<< =================== >>>>>>
Q. 118: (Level K2) In an Agile project, out of the following which would best denote
product quality at the end of iteration 6 of a new system release consisting of 8
iterations?
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.
Explanation in favor of the correct answer:
One of the best metric for product quality is the customer satisfaction by
increased productivity. Customer satisfaction could be through beta testing
of the final releases.
<<<<<< =================== >>>>>>
Q. 119: (Level K2) In the final days of sprint tests, execution is blocked due to a test
environment related issue which is escalated to the environment team.
Option (B) is True – as Burndown charts show the planned progress and
release date together with the actual progress of the user stories.
Option (C) is False – as the number of completed stories will tell the team
velocity for that sprint.
Option (D) is False – as the Test Summary report contains the summary of
test activities and final test results.
<<<<<< =================== >>>>>>
Q. 125: (Level K2) “Test automation is important to manage regression risk in
Agile projects”
Which out of the following TWO reasons support the above statement?
i. To eliminate regression risk due to high code churn.
ii. To ensures that all previous iterations’ stories are tested.
iii. To receive immediate feedback on overall product quality.
iv. So the team can make changes to previously delivered features to meet
the customer’s needs.
v. It gives the team more time to spend on the current iteration activities.
A. i and ii
B. iv and v
C. iii and iv
D. ii and v
Explanation in favor of the correct answer:
Statement (i) is False – as automation can reduce the regression risk but
cannot guarantee to eliminate all regression risk.
Statement (ii) is False – as it is not feasible to automate all of the tests and
it is also not possible to retest/rerun all of the test cases from all of the
previous iteration.
Statement (iii) is False – as automated acceptance test results can provide
feedback on product quality with respect to the regression since the last
build, but they do not provide the status of overall product quality.
Statement (iv) is True – as automation reduces the regression test effort
so the team can accept and make changes to previously delivered features
to meet the customer’s needs.
Statement (v) is True – as automation reduces the regression test effort so
the team can work on tasks from the current iteration
<<<<<< =================== >>>>>>
Q. 126: (Level K2) Out of the following which can be used to reduce
regression risk due to high code churn in Agile projects?
A. Automation done for test data generation.
B. Automation done for unit tests.
C. Automation done to compare data outputs.
D. Automation done to restore test environment to baseline.
Explanation in favor of the correct answer:
Automated unit tests will provide rapid feedback on product quality and
can reduce the risk of regression. Automation for test data generation,
comparing data output and restoring test environment will allow the team
to spend more time in developing and testing new features but will not
reduce the risk of code chum.
<<<<<< =================== >>>>>>
Q. 127: (Level K2) Which out of the following TWO statements justify the
high investment on Automation in Agile projects?
i. Test Automation helps maintain velocity without incurring a large amount
of technical debt.
ii. Test Automation helps to detect the defects early in the project cycle.
iii. Automated acceptance test results can provide immediate feedback on
overall product quality.
iv. Test Automation gives the testers more time to test new features and
functions in the current iteration.
v. Test Automation ensures that all test cases from the previous iterations
are tested.
A. i and v
B. i and iv
C. iii and iv
D. ii and v
Explanation in favor of the correct answer:
Statement (i) is True – as changes in each iteration will require more and
more regression testing. If automation was not used, then the team’s
velocity would be reduced or the Technical debt will increase.
Statement (ii) is False – as this is not a reason to introduce automation on
a project.
Statement (iii) is False – as automated acceptance test results can provide
feedback on product quality with respect to the regression since the last
build but they do not provide the status of overall product quality.
Statement (iv) is True – as automation reduces the regression test effort
so the testers can work on other tasks from the current iteration.
Statement (v) is False – as it is not feasible to automate all the tests and it
is not possible to retest/rerun all the test cases from all the previous
iterations.
<<<<<< =================== >>>>>>
Q. 128: (Level K2) The Agile team has created an automation acceptance test
suit to manage regression risk due to frequent changes in the project. This is
now part of the continuous integration full system build, what should be the
frequency of run?
A. Daily
B. Weekly
C. Each code check
D. At least once in the sprint
Explanation in favor of the correct answer:
Automation acceptance test suit should be run at least daily. To explain
further, the automation acceptance test suit should not be run with each
code check-in as they take longer to run than automated unit tests and
could slow down the code check-in.
<<<<<< =================== >>>>>>
Q. 129: (Level K2) The Agile team is developing the automated build
verification tests to provide instant feedback on the software after
deployment.
Out of the following which TWO tests should be part of the Automated build
verification tests?
1. All tests to cover critical system functionality.
2. All tests which have previously failed
3. All tests from the previous iteration
4. All tests to cover integration points.
A. 2 and 3
B. 1 and 4
C. 2 and 4
D. 1 and 2
Explanation in favor of the correct answer:
Statement (1) is correct – as all tests to cover critical system functionality
should be part of the Automated build verification tests to make sure that
the build is stable for testing.
Statement (2) is incorrect – as all tests which have previously failed are not
necessarily part of the Automated build verification tests.
Statement (3) is incorrect – as all tests from the previous iteration are not
necessarily part of the Automated build verification tests.
Statement (4) is correct – as all tests to cover integration should be part of
the Automated build verification tests to make sure that the build is stable
for testing.
<<<<<< =================== >>>>>>
Q. 130: (Level K2) Out of the following which would need to be done first to
minimize the introduction of regression risk when a feature which has already
been delivered is changed in the current iteration?
A. The team should increase the amount of test automation to reduce
regression risk.
B. Automate all the tests for that feature and add them to the automated
regression test suite.
C. The changes should be manually tested now and later added to the
automation test suit.
D. Do the impact analysis to find out all of the manual and automated tests
impacted by this change to meet the new acceptance criteria.
Explanation in favor of the correct answer:
Option (A) is False – as a review of the changes are required first before
making any decision. It is unknown if additional automation is required.
Option (B) is False – as a review of the changes are required first before
making any decision.
Option (C) is False – as a review of the changes are required first before
making any decision since the tester would not know what new tests would
be required for these changes.
Option (D) is True – as this is the initial task to be performed before a
decision about any other changes can be made.
Q. 131: (Level K2) In Agile projects, there is a greater need for testers to
understand and be competent in white box testing.
Which out of the following TWO reasons best indicate why this is a more
important skill on Agile projects than on traditional projects?
i. Agile team is cross-functional so all members can help in each other’s
task. This also enables them to help developers.
ii. In Test Driven Development testers have to write the unit test first so the
developers can write the code.
iii. Agile testing relies more on white box testing than black box testing.
iv.
Testers can improve the program logic by pair programming.v. In Agile
projects, testers often work closely with developers for automation of unit
tests and review of the code.
A. i & ii
B. ii & v
C. iv & v
D. i & v
Explanation in favor of the correct answer:
Statement (i) is True – Obvious definition of the agile team.
Statement (ii) is False – as in Test Driven Development, Automated unit
tests are written by the developers, not by testers.
Statement (iii) is False – as Agile projects require both white box and black
box testing.
Statement (iv) is False – as Pair programming is typically done using two
developers; testers are not expected to improve program logic.
Statement (v) is True – Obvious definition of agile project.
<<<<<< =================== >>>>>>
Q. 132: (Level K2) Out of the following which are necessary skills for a Tester
working on agile projects?
i. Competent in test automation.
ii. Competent in alpha/ beta testing.
iii. Competent in experience-based testing.
iv. Competent in unit testing.
A. i, ii and iii
B. i, ii, iii and iv
C. i and iii
D. i, iii and iv
Explanation in favor of the correct answer:
Statement (i) is True – as in agile, a lot of emphases is laid on automation
tests so it is an essential skill for a tester.
Statement (ii) is False – as Alpha / Beta Testing is done by customers.
Testers can assist, but it is not a necessary skill.
Statement (iii) is True – as in agile, a lot of emphases is laid on exploratory
testing so it is an essential skill for a tester.
Statement (iv) is False – as Unit Testing is done by developers. Testers can
assist but it is not a necessary skill
<<<<<< =================== >>>>>>
Q. 133: (Level K2) Why is test automation a more necessary skill on Agile
projects for Testers than on traditional projects?
Select TWO reasons from following statements.
i. Features can change in future iterations. Automated tests are necessary
to reduce the regression risk due to rapid changes.
ii. All feature validation testing should be done in the same iteration. In
practice, that can only be realized by automated tests.
iii. Regression testing is a parallel process occurring throughout the
iteration. This can only be achieved by automating the tests.
iv. All tests for the iteration are required to be finished in the iteration. This
is not possible without Automation tests.
v. Agile testing relies more on white box testing than black box testing.
A. i & ii
B. ii & v
C. iv & v
D. i and iii
Explanation in favor of the correct answer:
Statement (i) is True – as automated tests are required to keep up with
frequent changes.
Statement (ii) is False – as feature validation tests are mostly done
manually.
Statement (iii) is True – as this involves re-running the automated unit and
feature verification tests from the current and previous iterations, usually
via a continuous integration framework.
Statement (iv) is False – as automation acceptance tests are not used to
finish all the testing In the current iteration they primary use is to make sure
the functionality is not impacted due to new changes in the following
iterations.
Statement (v) is False – as neither automation nor manual testing is more
important than the other in Agile projects.
<<<<<< =================== >>>>>>
Q. 134: (Level K2) Out of the following which is NOT a typical task
performed by the tester within Agile team?
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.
Explanation in favor of the correct answer:
In agile team scrum master typically updates the burndown charts and not
the tester.
<<<<<< =================== >>>>>>
Q. 135: (Level K2) Out of the following which is NOT a test related
organization risk which Agile organizations may encounter?
A. Testers work so closely to developers that they lose the appropriate
tester mindset.
B. Testers become tolerant about inefficient, ineffective, or low-quality
practices within the team.
C. Testers cannot keep pace with the incoming changes in time-
constrained iterations.
D. Testers spend more time on Automation related activities rather than on
testing.
Explanation in favor of the correct answer:
Option (A), (B) & (C) are incorrect – as it is true that Agile organizations
may encounter these type of test-related risks.
Option (D) is correct – as this is not a test related organization risk.
<<<<<< =================== >>>>>>
Q. 136: (Level K2) Which one of the following is a test related organization
risk that Agile organizations may encounter?
A. Testers work so closely with developers that they lose the appropriate
tester mindset.
B. Testers managing the test environment and the test data.
C. Testers providing feedback on process quality.
D. Testers helping the team on non-testing activities.
Explanation in favor of the correct answer:
Option (A) is True – as Agile organizations may encounter this test related
risk.
Option (B), (C) and (D) are False – as these are not test related organization
risks. All these are required from an Agile tester.
<<<<<< =================== >>>>>>
Q. 137: (Level K2) Which out of the following TWO are activities for the
Tester on Agile projects but not necessarily on traditional projects?
i. Testers provide feedback on process quality.
ii. Understand, implement and update the test strategy.
iii. Actively collaborate with developers and business stakeholders.
iv. Testers provide feedback on product quality.
v. Automate and maintain Automation tests.
A. i & iii
B. iii & v
C. i & v
D. ii and iv
Explanation in favor of the correct answer:
Statement (i) is True – as in agile, testers provide feedback on process
quality by proactively participating in the team retrospectives, suggesting
and implementing improvements.
Statement (ii), (iii) & (iv) are False – as all these are required for both Agile
as well as traditional projects.
Statement (v) is True – as in agile, automation is required, therefore part of
the tester’s role is to produce automation scripts, run and maintain them.
<<<<<< =================== >>>>>>
Q. 138: (Level K2) Out of the following which is NOT a typical task
performed by the tester on Agile project?
A. To prepare and report the test coverage.
B. To prepare the test status report.
C. To produce the burndown charts.
D. To prepare the test strategy.
Explanation in favor of the correct answer:
Option (A), (B) and (D) are incorrect – as it is true to say that all these
activities are expected from an agile tester.
Option (C) is Correct – as in agile, Scrum Master is responsible to produce
and update the burndown chart based on the information provided by the
rest of the team.
<<<<<< =================== >>>>>>
Q. 139: (Level K2) Out of the following which is NOT a typical task
performed by the tester on Agile project?
A. Ensuring proper use of testing tools.
B. Measuring and reporting test coverage.
C. To maintain the Agile task board for the team.
D. Configure and manage the test environment and the test data.
Explanation in favor of the correct answer:
Option (A), (B) and (D) are incorrect – as it is true to say that all these
activities are expected from an agile tester.
Option (C) is Correct – as in agile, the tester is only responsible to maintain
testing tasks on the Agile task board. Each member of the Agile team is
responsible to maintain their respective tasks on the Agile task board.
<<<<<< =================== >>>>>>
Q. 140: (Level K2) Which tasks are typically expected of a tester within the
Agile team?
i. Decide on user acceptance.
ii. Understanding, implementing and updating the test strategy.
iii. Prepare burndown charts
iv. Configuring, using, and managing test environments and test data.
v. Decide on the priority of the user story.
A. i and iii
B. ii and iii
C. ii & iv
D. ii & v
Explanation in favor of the correct answer:
Statement (i) is False – as this task is a collaborative effort for the whole
team.
Statement (ii) is True – as this activity is expected out of an agile tester.
Statement (iii) is False – as in agile, Scrum Master is responsible to
produce and update the burndown chart from the information supplied by
the rest of the team,
Statement (iv) is True – as this activity is expected out of an agile tester.
Statement (v) is False – as the business users decide the priority on user
stories.
Q. 141: (Level K2) Which tasks are typically expected of a tester on the 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.
A. i & iii
B. ii & iii
C. ii & iv
D. ii & v
Explanation in favor of the correct answer:
Statement (ii ) & (iv) are True – as these activities are expected out of an
agile tester.
<<<<<< =================== >>>>>>
Agile Tester Certification syllabus V2014 Chapter -3:
(Agile Testing Methods, Techniques, and Tools)
Q. 142: (Level K1) Which statement is TRUE in respect to exploratory testing
in Agile projects?
A. Testers having good knowledge of the system should perform
exploratory testing.
B. The Independent Test team should be engaged in exploratory testing
C. Users engaged in Alpha testing should perform exploratory testing
D. Automated tests should be used for exploratory testing.
Explanation in favor of the correct answer:
Option (A) is True – as the tester needs a good understanding of how the
system is used.
Option (B) is False – as exploratory testing is carried out by testers having
good knowledge of the system so they can get the desired results in limited
time.
Option (C) is False – as exploratory testing is done before the user
acceptance phase.
Option (D) is False – as automation of exploratory testing is not possible as
test design and execution happens in parallel
<<<<<< =================== >>>>>>
Q. 143: (Level K1) Out of the following which statements best reflects one of
the values of the Agile Manifesto?
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 Agile project.
<<<<<< =================== >>>>>>
Q. 144: (Level K1) Out of the following which statements about Test Driven
Development (TDD) is FALSE?
A. Test Driven Development is a ”test first” approach to develop reusable
automated tests.
B. The Test Driven Development cycle is continuously used until the
software product is released.
C. Test Driven Development helps to document the code for future
maintenance efforts.
D. The result of Test Driven Development are test classes used by the
developer to develop test cases
Explanation in favor of the correct answer:
As per the primary definition of Test Driven Development, it facilitates
developers in creating test cases with the help of test classes.
<<<<<< =================== >>>>>>
Q. 145: (Level K1) Out of the following which statements about Acceptance
Test-Driven Development is FALSE?
A. Acceptance Test-Driven Development allows a developer to focus on
testing the code based on the expected behavior of the software.
B. Tests are created once the user story is analyzed, discussed and written
by the Agile team.
C. Acceptance Test-Driven Development defines acceptance criteria and
tests In the creation of the user stories.
D. Acceptance Test-Driven Development is a test-first approach, test cases
are created prior to implementing the user story.
Explanation in favor of the correct answer:
Option (A) is True – as this is true of Behaviour Driven Development, and
not Acceptance Test-Driven Development.
Option (B), (C) & (D) are False – as all these are true for Acceptance Test-
Driven Development.
<<<<<< =================== >>>>>>
Q. 146: (Level K1) Out of the following which statements about Test Driven
Development (TDD) is FALSE?
A. The Test-Driven Development process starts with a developer adding a
test that captures the concept of the desired function of a small piece of
code.
B. In Test-Driven Development, developers write the code and run the test
in a tight loop until the test passes.
C. Test-Driven Development allows the developer to collaborate with other
stakeholders, including testers, to define accurate unit tests focused on
business needs.
D. In Test-Driven Development, developers refactor the code after the test
is passed, re-running the test to ensure it continues to pass against the
refactored code.
Explanation in favor of the correct answer:
Option (A), (B) & (D) are False – as all these are true for Test-Driven
Development.
Option (C) is True – as this is true of behaviour-driven development and not
for Test-Driven Development.
<<<<<< =================== >>>>>>
Q. 147: (Level K1) The term “velocity” refers to Out of the following which?
A. A Velocity chart shows the sum of estimates of the work delivered
across iterations; this may be used while selecting the stories for the next
iteration
B. A Velocity chart shows the degree to which the source code of a
program is tested by a particular test. This may be used to show the code
coverage
C. A Velocity chart shows the count of the number of defects discovered
during a given period. This may be used as criteria for stopping the testing.
D. A Velocity chart shows the number of source code changes per iteration;
this may be used to know the code coverage
Explanation in favor of the correct answer:
Option (A) is True – as this is true for velocity chart.
Option (B) is False – as this is a code coverage chart, not a velocity chart.
Option (C) is False – as this is a defect discover rate chart, not a velocity
chart.
Option (D) is False – as this is a Code Churn chart, not a velocity chart.
<<<<<< =================== >>>>>>
Q. 148: (Level K1) What does the term ‘Test Pyramid’ refer to and illustrate
situations for?
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.
Explanation in favor of the correct answer:
The agile test automation pyramid model graphically splits the types of
testing into three layers. The largest part of the pyramid structure is the
bottom layer typically includes unit testing, representing the idea that
automating it offers the best return on investment to the organization.
<<<<<< =================== >>>>>>
Q. 149: (Level K1) The concept of the Test Pyramid is based on Out of the
following which testing principles?
A. Early Testing.
B. Defect clusters.
C. Pesticide paradox.
D. Exhaustive testing is impossible.
Explanation in favor of the correct answer:
Option (A) is True – as the test pyramid is based on the testing principle of
early testing and eliminating defects as early as possible in the lifecycle.
Option (B) is False – as the test pyramid is not related to defect clustering.
Option (C) is False – as the test pyramid is not related to Pesticide
paradox.
Option (D) is False – as the test pyramid is not related to Exhaustive
testing.
<<<<<< =================== >>>>>>
Q. 150: (Level K1) Before beginning the first iteration of a project the team is
discussing the test strategy for automation.
Out of the following which is true with respect to Test Pyramid?
A. The team should aim to automate most of the unit/component tests
during the sprints.
B. The team should aim to automate most of the usability tests during the
sprints.
C. The team should aim to automate most of the exploratory tests during
the sprints.
D. The team should aim to automate most of the user story tests during the
sprints.
Explanation in favor of the correct answer:
The test pyramid emphasizes having more tests at the lower levels and a
decreasing number of tests at the higher levels.
Q. 151: (Level K1) The foundation layer of the ‘Test Pyramid’ is made up of
which tests?
A. Unit/component tests.
B. System level tests.
C. Integration level tests
D. Acceptance level tests
Explanation in favor of the correct answer:
The test levels from the base of the pyramid to the top are unit /
component, integration, system, and acceptance
<<<<<< =================== >>>>>>
Q. 152: (Level K1) What does the term ‘Test Pyramid’ refer to in Agile
projects?
A. It is used to help the team understand the
testing coverage for the user story/feature.
B. It can help the team determine how much testing time will be required
for each user story.
C. The number of automated tests are greater at the unit level and
decrease at the higher levels.
D. It can help the team to find the impacted automated tests due to
changes in a feature.
Explanation in favor of the correct answer:
Option (A) is False – as the workload for each sprint has nothing to do with
the Test Pyramid concept.
Option (B) is False – as the testing time for each user story has nothing to
do with the Test Pyramid concept.
Option (C) is True – as the test pyramid emphasizes having more tests at
the lower levels and a decreasing number of tests at the higher levels.
Option (D) is False – as the number of impacted automated tests due to
changes in a feature has nothing to do with the Test Pyramid concept.
<<<<<< =================== >>>>>>
Q. 153: (Level K1) Out of the following which statements about Behaviour-
Driven Development is FALSE?
A. Behaviour-Driven Development allows a developer to focus on testing
the code based on the expected behavior of the software.
B. Behaviour-Driven Development allows the developer to collaborate with
other stakeholders, including testers, to define accurate unit tests focused
on business needs.
C. In Behaviour-Driven Development, automated test cases are created
before coding starts.
D. The result of Behaviour-Driven Development is test classes used by the
developers to develop the test cases.
Explanation in favor of the correct answer:
Option (A), (B) & (D) are False – as all these are true for Behaviour-Driven
Development
Option (C) is True – as this is true for Test Driven Development and not for
Behaviour-Driven Development.
<<<<<< =================== >>>>>>
Q. 154: (Level K1) 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?
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.
Explanation in favor of the correct answer:
It is the responsibility of the tester to bring the issue to the notice of the
team. Then the team conducts risk analysis and plans regression testing
with all browsers to be done by the tester.
<<<<<< =================== >>>>>>
Q. 155: (Level K2) Consider the following user story: “As the president, any
data I upload should not be viewable by any other user of the system”.
In 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?
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.
Explanation in favor of the correct answer:
The team must not decide based upon the size estimates from customers
and developers rather offer weightage to the judgment of the tester and
seek clarifications in support of his / her opinion and plan for more
discussions.
<<<<<< =================== >>>>>>
Q. 156: (Level K2) Consider the following user story:
“The social networking application should now check for the user age and
only the users of age 18 or above should be able to register”
And the associated test cases:
Test Case 1: Check the Save Method 0 saves the user age to the database.
Test Case 2: Verify an existing user is able to access the social networking
site.
Test Case 3: A registered user is able to delete their social networking site
account.
Which TWO test quadrants would the above test cases be part of?
A. Q1 unit level, technology facing & Q2 system level, business facing
B. Q1 unit level, technology 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
Explanation in favor of the correct answer:
Q1 is Correct – as unit/component tests are part of the 1st quadrant.
Q2 is Incorrect – as these test cases are not system level tests.
Q3 is Correct – as these test cases are for user acceptance level tests.
Q4 is Incorrect – as these test cases are not for operation acceptance level
tests
<<<<<< =================== >>>>>>
Q. 157: ( agile value (1-4) with its traditional counterpart (i-iv).
1) Customer collaboration over.
2) Responding to change over.
3) Individuals and interactions over.
4) Working software over.
i) Processes and tools.
ii) Following a plan.
iii) Contract negotiation.
iv) Comprehensive documentation.
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
Explanation in favor of the correct answer:
Agile value (1) “Customer collaboration” relates to activity (iii) Negotiations
with the customer.
Agile value (2) “Response to change” relates to activity (ii) Implementation
of the plan.
Agile value (3) “Interactions with people” relates to activity (i) Decision on
processes to be followed and tools to be used.
Agile value (4) “working software” relates to activity (iv) Documentation
work.
<<<<<< =================== >>>>>>
Q. 158: (Level K2) Which out of the following TWO statements demonstrate
effective use of the testing quadrants?
1. The testing quadrants model and its variants help to ensure that all
important test types and test levels are included in the development
lifecycle
2. 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.
3. The testing quadrants model provides a way to differentiate and
describe the types of tests to all stakeholders, including developers,
testers, and business representatives.
4. Testing quadrants are used for risk analysis; with the lower level
quadrants representing a lower risk to the customer.
5. Testing quadrants can be used to find out whether the story acceptance
criteria is testable.
A. 1 and 4
B. 2 and 3
C. 2 and 4
D. 1 and 3
Explanation in favor of the correct answer:
Statement (1) is True – as the testing quadrants can be used to ensure that
all test types and test levels are covered.
Statement (2) is False – as the testing quadrants cannot be used as
metrics since not all test levels/types are applicable to the system under
test.
Statement (3) is True – as the testing quadrants can be used as an aid to
describing the types of tests and their purpose to all stakeholders.
Statement (4) is False – as the testing quadrants have no correlation with
risk level.
Statement (5) is False – as testing quadrants are not related to story
acceptance criteria testability.
<<<<<< =================== >>>>>>
Q. 159: (Level 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 the 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 the 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?
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
An application calculates the variable interest rate for a bank account based
on the following criteria:
# 1.5 percent for the first Rs.1,000 credit
# 2.0 percent for the next Rs.1,000
# 1.5 percent for the rest.
Out of the following which is the best black box test design technique for
the user story?
A. State Transition testing: Test the following states for Account – First
credit, Second credit, Rest.
B. Decision tables: Test the following conditions – User credit first Rs.1000;
Interest calculated as 1.5 % etc.
C. Boundary Value Analysis: Test the following boundaries -1000, 1001,
2000, 2001
D. Use Case Testing: Actor= customer; Prerequisites=customer has
account, deposit amount ; Post conditions= Interest calculated
Explanation in favor of the correct answer:
Option (A) is False – as the focus of this user story is not on the state of
the system; instead, the expectation is to test the right interest is calculated
based on the account balance.
Option (B) is False – as the focus of this user story is not of interest
calculated; the expectation is to test the right interest is calculated based
on the account balance.
Option (C) is True – as BVA is the best option when testing different
boundaries.
Option (D) is False – as the focus of this user story is not on whether the
Interest is calculated; the expectation is to test the right interest is
calculated based on the account balance.
<<<<<< =================== >>>>>>
Q. 190: (Level K3) Review the following User Story for searching for a health
care provider on the health insurance website:
“As a customer, I can find a health care provider based on the Region,
Category, or suburb information”
Out of the following which can be considered as relevant acceptance test
cases?
i. The search window should display within a reasonable time.
ii. Select the Region from the drop-down and click the Search button.
iii. Select the Category from the drop-down and click the Search button.
iv. Select the suburb from the drop-down and click the Search button.
v. Select the Region, category, and suburb from the drop-down and click the
Search button.
vi. Select the healthcare provider type and click the search button.
A. i, ii, iv
B. ii, iii, iv
C. ii, iv, vi
D. iii, iv, vi
Explanation in favor of the correct answer:
Test case (i) is incorrect – as the user story does not mention performance
requirements.
Test case (ii), (iii) & (iv) are correct – as all these tests are specific to the
search service provider function.
Test case (v) is incorrect – as the user story is specific to search based on
either Region, Category, or suburb information. The question is specific to
Either / OR not Any / All
Test case (vi) is incorrect – as the user story is specific to the search based
on the Region, Category, or suburb information.
Q. 191: (Level K3) In one of the Agile projects, testers have been asked to plan
exploratory testing.
Out of the following which approaches are NOT correct for Exploratory
testing?
A. Testers will do the risk analysis and test the critical things the tester and
user think could go wrong or the potential problems that will make people
unhappy.
B. Testers will test based on the model of how software should behave.
The functions which the customers are more interested in should be tested
first.
C. Testers will test based on their past experience of how similar systems
failed in predictable patterns. These experiences can be refined into a test
and explored.
D. Tests will not be planned as the testers have already tested these stories
and should progress the test based on their intuition.
Explanation in favor of the correct answer:
Option (A), (B) & (C) is incorrect – as this is true for exploratory testing.
Option (D) is correct – False – There is a plan required for exploratory
testing.
<<<<<< =================== >>>>>>
Q. 192: (Level K3) The Test Manager has organized a meeting with the test
team to explore the possibility of exploratory testing after the final iteration
for one of the Agile teams. He has shared the following suggestion with the
testers.
Which TWO of your manager’s conclusions are NOT correct?
i. The Independent test team with be engaged in the testing of user stories.
There will be a fixed time to complete the exploratory testing and there is
no need to document tests or test results.
ii. Testers will do the risk analysis and will plan the tests of critical things
that can go wrong or the potential problem that will make people unhappy.
iii. Business representatives will be used for exploratory testing. They will
use the system like the customer would on a day-to-day basis. Testers can
help them prioritize and log the defects.
iv. An experienced tester will be used for exploratory testing. Tests should
make sure that functionality is correct and to include negative testing.
Documentation is not necessary, but defects need to be logged in the
defect tracking tool.
A. i & ii
B. ii & iv
C. iii & iv
D. i & iii
Explanation in favor of the correct answer:
Statement (i) is False – as independent testers are not suitable for
exploratory testing.
Statement (ii) is True – as this is true for exploratory testing.
Statement (iii) is False – as this is an example of user acceptance testing,
not exploratory testing.
Statement (ii) is True – as this is true for exploratory testing.
<<<<<< =================== >>>>>>
Q. 193: (Level K1) Agile team is looking for a tool to manage requirements
and traceability; additional features should be managing dashboards on
product status & recording conversations
Out of the following which will be suitable for this purpose?
A. Configuration Management (CM) tool.
B. Wild.
C. Test Charter.
D. Continuous Integration (CI) tool
Explanation in favor of the correct answer:
Option (A) is False – as Configuration Management (CM) tool will be
suitable for storing source code and other test work products
Option (B) is True – as This is one of many purposes of a wild tool.
Option (C) is False – as Test Charter will be suitable for exploratory testing.
Option (D) is False – as Continuous Integration (CI) tool will be suitable for
visibility on build status and automatic reporting.
<<<<<< =================== >>>>>>
Q. 194: (Level K1) Agile team wants to build and share an online knowledge
base on various aspects of the project.
Out of the following which tools will be best for that purpose?
A. Continuous Integration (CI) tool.
B. Wiki.
C. ALM.
D. Configuration management (CM) tool
Explanation in favor of the correct answer:
Option (A) is False – as Continuous Integration (CI) tool provides quick
response about the build quality and details about code changes.
Option (B) is True – as Wiki allows teams to build a knowledge base on
tools and techniques for development and testing activities.
Option (C) is False – as ALM tool provides visibility into the current state of
the application, especially with distributed teams.
Option (D) is False – as Configuration management (CM) tool is suitable
for providing traceability between versions of software and the tests used.
<<<<<< =================== >>>>>>
Q. 195: (Level K3) The following is a User Story for an online, money transfer
applications Receiver Bank Account:
“As an online banking customer When I am initiating an online money
transfer, Then the system should validate the Bank code and Bank Account
Number of the Receiver and notify if they are invalid”
Out of the following which is relevant acceptance test cases?
i. Log in as a customer, enter an invalid bank code to see the error message
ii. Log in as a customer, check the customer account balance is displaying
correctly before and after the transfer.
iii. Log in as a customer, enter a valid bank code and bank account number;
no error message should be displayed.
iv. Log in as a customer, enter an invalid bank account number to see the
error message.
v. Log in as a customer, enter a valid bank code to see the Bank name from
the list.
A. i, ii, iv
B. i, iii, iv
C. ii, iv, v
D. ii, Hi, iv
Explanation in favor of the correct answer:
Test case (i), (iii) & (iv) are correct – as all these tests are specific to check
the bank code and bank account number validation.
Test case (ii) is incorrect – as the user story does not mention Account
balance checks.
Test case (v) is incorrect – as the user story does not mention displaying
the Bank Name when entering a valid Bank code.
<<<<<< =================== >>>>>>
Q. 196: (Level K1) A new agile team wants to use their single server to build
multiple testing and development environments.
Out of the following which can be used for this purpose?
A. Mind maps.
B. ALM.
C. Electronic task boards.
D. Virtualization tools.
Explanation in favor of the correct answer:
Option (A) is False – as Mind maps can be used to quickly design and
define tests for a new feature.
Option (B) is False – as ALM tool can be used to provide visibility into the
current state of the application, especially with distributed teams.
Option (C) is False – as Electronic task boards are used to manage and
track user stories, tests, and other tasks throughout each sprint.
Option (D) is True – as Virtualization tools allow a single physical server to
operate as many separate, smaller resources which can be used for
development and testing purposes.
<<<<<< =================== >>>>>>
Q. 197: (Level K1) Out of the following which is NOT a purpose of a
Continuous Integration (CO tool on the Agile project?
A. To provide quick feedback on code quality.
B. To provide assistance to testers for integration testing.
C. To provide a quick response to the build quality and details about code
changes.
D. To provide automatic reporting.
Explanation in favor of the correct answer:
Option (A) is False – as it is true to say that this would be one of the
purposes of Continuous Integration tools (CI) tool.
Option (B) is True – as this is not the purposes of a Continuous Integration
(CI) tool
Option (C) is False – as it is true to say that this would be one of the
purposes of a Continuous Integration (CI) tool.
Option (D) is False – as it is true to say that this would be one of the
purposes of a Continuous Integration (CI) tool.
<<<<<< =================== >>>>>>
Q. 198: (Level K1) Out of the following which is one of the purposes of a test
Charter?
A. Test Charter helps the testers in test data generation for testing.
B. Test Charter guides the testers in exploratory testing.
C. Test Charter provides a knowledge base on tools and techniques for
development and testing activities.
D. Test Charter provides a quick response to the build quality and details
about code changes.
Explanation in favor of the correct answer:
Option (A) is False – as this would be one of the purposes of a data
generation tool
Option (B) is True – as this is one of many purposes of a Test Charter.
Option (C) is False – as this would be one of the purposes of a Wild.
Option (D) is False – as this would be one of the purposes of a Continuous
Integration (CI) tool
<<<<<< =================== >>>>>>
Q. 199: (Level K1) Out of the following which is one of the purposes of an
Application Lifecycle Management (ALM) tool on Agile project?
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 a quick response to 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.
Explanation in favor of the correct answer:
The Application Lifecycle Management tool are deployed for acquiring the
in depth knowledge about the state of the application.
<<<<<< =================== >>>>>>
Q. 200: (Level K1) Out of the following which is NOT a principle of
continuous integration?
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.