Agile Testing

In an Agile project, when is software first expected to be delivered that will provide value to the customer?

• At the end of an epic

• At the end of an iteration

• At the end of a release

• At the end of the project

What is the proper order of planning?

• Release, then iteration

• In most Agile projects only one type of planning is done, either release or iteration

• Iteration, then release

• Both occur at the same time

What types of automated testing activities are included in the continuous integration process?

• Unit only

• Unit and integration testing

• Unit and regression testing

• Unit, integration, and system testing

What does a burndown chart measure?

• The amount of work still to be done against the time allocated

• Return on investment

• Schedule time against expected budget

• How quickly activities move between stations

In a retrospective meeting, who should provide input into the testing activities on the project?

• Everyone on the team

• Only the developers

• Only the testers

• Everyone but the testers

What does it mean when a feature is classified as “done”?

• It has been developed, integrated and tested.

• It has been developed, integrated, tested and released to production.

• It has been developed and integrated.

• It has been developed.

Agile is

• A software development process

• An adjective

• A mindset

• A set of best practices

Agile Testing is

• The responsibility of the QA role

• A collaborative team effort

• Performed at the end of each sprint

• Not required until the hardening sprint

100% requirements testing achieves good testing.

• True

• False

Zero defect code is a goal of Agile testing.

• True

• False