Question Bank

Complete

• The "entire team" is responsible for quality in Agile projects.

• XP teams use "slack time" to pay down "technical debt" by refactoring code or doing
research.
• A cross-functional team in XP releases "working software" frequently.
• Agile projects have short iterations; thus, the project team receives "regular" and
"frequent" feedback on product quality throughout the SDLC.
• The general objective of "Kanban" is to visualize and optimize the flow of work within a
value-added chain.
• One programmer plays the role of "driver" and focuses on clean code, and compiles
and runs. The second one plays the role of "navigator" and focuses on the big picture
and reviews code for improvement or refactoring.
• There are 2 levels of plans in XP: "release planning" and "iteration planning". In both
levels, there are 3 steps: "exploration", "commitment", and "steering".
• User stories must address "functional" and "non-functional" characteristics. Each story
includes "acceptance criteria" for these characteristics used to decide when a task is
"completed".
• All team members, testers and non-testers, can "collaborate" on both testing and non-
testing activities.
2
Complete

• When the regression testing is automated, the Agile testers are freed to
concentrate their manual testing on" exploratory testing", and " targeted testing "of
defect fixes.
• In agile projects, no feature is considered done until it has been "tested" and
"integrated" with the system.
• "Stabilization" iterations occur periodically to resolve any remaining defects and
other forms of "technical debt".
• Because of the heavy use of test automation, a higher percentage of the manual
testing on Agile projects tends to be done using "exploratory" testing.
• While developers will focus on creating unit tests, testers should focus on creating
automated "functional" and "integration" tests.
• Changes to existing features have testing implications, especially "regression"
testing implications.
• During an iteration, any given user story will typically progress sequentially through
the following test activities: "acceptance testing" and "regression testing".
3
Complete

• In test pyramid, "unit" and "integration" level tests are automated and created
using "developer-focused" tools. At "service" and "UI" levels, automated tests
are created using "tester-focused" tools.
• Testing quadrants apply to --- testing only.
• "Risk-based" strategies can be used by the testers in Agile teams to help
determine the acceptable number of test cases to execute.
• Iteration starts with iteration "planning", which ends in tasks on a task board.
These tasks can be "prioritized" in part based on level of "risk" associated with
them. The aim is to know which tasks should start "early" and involve more
"testing" effort.
• During iteration planning, team assesses each identified risk, which includes two
activities: "categorizing the risk" and determining its "level of risk" based on the
"impact" and the "likelihood" of defects.
• Information from the "product backlog" is used during poker planning sessions
to determine priorities of items to be completed in the "iteration".
• The main part of the lifecycle cost often comes from "maintenance ".
4
Complete

• During exploratory testing, results of the most recent tests guide the "next set of
tests".
• "testing session" is an uninterrupted period of testing, could last from 60-120
mints.
• Test sessions include "exploratory" session to learn how it works, "functional"
session to evaluate functionality, and "edge case" for corner cases, scenarios,
and interactions.
• "Agile Test Dashboard" provides a visual representation (via metrics, charts, and
dashboards) of the current state of each user story, the iteration, and the
release, allowing all stakeholders to quickly check status.
• Some Agile teams opt for an all-inclusive tool called an "Agile management tool"
that provides relevant features (such as task boards, burndown charts, and user
stories).
• " Wikis" allow teams to build up an online knowledge base on tools and
techniques for development and testing activities.
5
Complete

• Risk of introducing regression in Agile development is high due to extensive

"changes". To maintain velocity without incurring a large amount of "technical
debt", it is critical that teams invest in "test automation" at all test levels early.
• It is critical that all test assets are kept up to-date with each "iteration".
• Testers need to allocate time in each "iteration" to review manual and
automated test cases from previous and current iterations to select test cases
that may be candidates for the "regression suite".
• "Exploratory testing", "Automated testing", and "Acceptance testing" are three
complementary techniques in use among Agile teams for testing across
various test levels.
• Benefits of test-driven development include "faster feedback", "reduced defect
rates", and "improved code quality".
• Results of BDD are "automatically" used by the developer to develop test
cases.
• BDD is concerned primarily with the specification of the behaviour of the
system under test as a whole, thus suited for "integration" and "acceptance"
testing.
6
 Replace with Key Term(s)

• Release that helps developer team and on-site customer to demonstrate product
and focus only on least amount of work that has highest priority.(small release)
• XP team is not doing actual development during this time but acts as a buffer to
deal with uncertainties and issues. (iteration zero)
• Planning level where the requirements and features that can be delivered into
production are decided based on priorities, capacity, estimations and risks factor
of the team to deliver.(release planning)
• In Kanban, the amount of parallel active tasks is strictly limited. This is controlled
by the maximum number of tickets allowed for a station and/or globally for the
board.
• Methodology used in situations where work arrives in an unpredictable fashion or
when you want to deploy work as soon as it is ready, rather than waiting for other
work items. (kanban)
• Need to integrate changes made every few hours or on a daily basis so after
every code compilation and build we have to integrate it where all the tests are
executed automatically for the entire project.(Continuous Integration.)
7
Replace with Key Term(s)

• Good practice to address defects remaining from previous iteration at

the beginning of the next iteration, as part of backlog for that
iteration.(fix bug first)
• Meeting held at the end of each iteration to discuss what was
successful, what could be improved in future iterations. (Retrospective)
• Small test or proof-of-concept workout. The outcome helps team to
consider validity of hypothesis, measure complexity of solution and feel
assured to estimate and build something primarily based on the
test. (Spike)
• Technique used by testers to write effective user stories and maintain
collaborative authorship.(Three Amigos)
• Agile form of requirements specifications that explain how the system
should behave with respect to a single, coherent feature or function.
(user story)
8
Replace with Key Term(s)
• Chart represents the amount of work left to be done against time allocated to the
release or iteration. (burndown chart)
• Testing adequate in Agile projects in case of limited time available for test analysis and
limited details of the user stories. (Exploratory Testing)
• Capture story cards, development tasks, test tasks created during iteration planning,
using colour-coordinated cards. (Visual Management Board)
• Testing technique creates a functional/behavioural test for a requirement that fails
because the feature does not exist.(TDD)
• Testing technique where stakeholders write acceptance tests in plain language based
on shared understanding of user story requirements.(BDD)
• Common effort estimation technique used in Agile projects.("Planning Poker" or "Agile
Estimating and Planning.")
• Activities that can only be performed in the system under certain conditions defined by
outside procedures and constraints.(preconditions)
• Testing where test design and test execution occur at the same time, guided by a
prepared test charter.(Exploratory testing)
• Tools used to store source code and automated tests, manual tests and other test work
9
products in same repository.