Testing in XP

Covering XP's four key testing features, test-first development, the benefits of writing tests before code, customer role in acceptance testing, automated testing frameworks, three reasons test-first doesn't guarantee thorough testing, build acceptance rules, and how user stories relate to tasks and test cases

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 203

Questions #: 10

Time: 10 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Why XP Emphasises Testing

1 pts

volume_mute

With incremental development there is no system specification that an external testing team can use to develop system tests. What is XP's response to this problem?

XP emphasises the importance of program testing and includes an approach that reduces the chances of introducing undiscovered errors — featuring test-first development, incremental test development from scenarios, user involvement, and automated test frameworks

XP defers all testing to the acceptance stage where the customer tests using real data

XP eliminates system testing entirely and relies on customer feedback after release

XP uses an independent external testing team who write tests based on user stories

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Test-First Development — The Core Idea

1 pts

volume_mute

The diagram below shows how test-first development works.

What is the key innovation of test-first development?

Tests are written by a separate external team to avoid bias

Tests are automatically generated from UML models before any coding begins

Tests are written after all code is complete to verify correctness

Tests are written before the code — this means you can run the test as the code is being written and discover problems during development

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Benefits of Writing Tests First

1 pts

volume_mute

Writing tests before writing code has two important benefits. Which of the following correctly describes both?

It allows developers to skip code reviews entirely

It eliminates all bugs and guarantees correct software

It implicitly defines both an interface and a specification of behaviour for the functionality being developed, reducing problems of requirements and interface misunderstandings; and it avoids test-lag where implementation gets further ahead of testing

It automatically generates production code from the test specifications

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Customer Role in XP Testing

1 pts

volume_mute

Complete the sentence about the customer's role in XP testing.

The role of the customer in the XP testing process is to help develop (1) tests for the stories that are to be implemented in the next release. In XP, acceptance testing, like development, is (2).

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Why Customer Involvement in Testing Is Difficult

1 pts

volume_mute

Relying on the customer to support acceptance test development is described as sometimes a major difficulty. Why?

People adopting the customer role often have very limited available time and may not be able to work full time with the development team — they may feel providing requirements was enough and be reluctant to get involved in testing

Customers are legally prohibited from writing software tests in most jurisdictions

Customers always write incorrect tests that slow development

Customer-written tests always fail because customers don't understand technical implementation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Automated Testing Frameworks

1 pts

volume_mute

Test automation is described as essential for test-first development. Complete the sentence.

Tests are written as executable components before the task is implemented. An automated test framework makes it easy to write executable tests and (1) a set of tests for execution. JUnit is a widely used example. As testing is automated, there is always a set of tests that can be quickly and easily executed — whenever any functionality is added to the system, the tests can be run and problems that the new code has introduced can be (2) immediately.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Reasons Test-First Doesn't Guarantee Thorough Testing

1 pts

volume_mute

Test-first development and automated testing usually results in a large number of tests. However, this approach does not necessarily lead to thorough program testing. Which of the following are the three stated reasons? Select all that apply.

It is difficult to judge the completeness of a test set — crucial parts of the system may not be executed and so remain untested

Programmers prefer programming to testing and sometimes take shortcuts — writing incomplete tests that do not check all possible exceptions

Customer-written acceptance tests always conflict with developer-written unit tests

Some tests can be very difficult to write incrementally — for example in a complex user interface where it is often difficult to write unit tests for display logic

Automated tests always produce false positives that mislead developers

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

New Build Acceptance Rule

1 pts

volume_mute

When a programmer builds the system to create a new version in XP, what rule must be satisfied before the new build is accepted?

The new build must pass code style checks before any tests are run

The new build is accepted only if all existing automated tests as well as the tests for the new functionality execute successfully

The customer must manually approve every change before integration

The new build must have fewer lines of code than the previous version

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Story Cards, Tasks, and Test Cases

1 pts

volume_mute

How do user stories, tasks, and test cases relate to each other in the XP testing process?

Tasks are written by the customer and converted to test cases by the development team without reference to user stories

User stories are converted directly to test cases without breaking them into tasks

User stories are broken down into tasks by the development team; each task generates one or more unit tests that check the implementation described in that task

Test cases are written independently of user stories by the external testing team

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Tests Must Pass After Integration

1 pts

volume_mute

True or False: In XP, when new code is integrated into the system, it is acceptable for some existing tests to fail temporarily while the new functionality is stabilised.

False

True

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Why XP Emphasises Testing

Correct Answer

Explanation

Test-First Development — The Core Idea

Correct Answer

Explanation

Benefits of Writing Tests First

Correct Answer

Explanation

Customer Role in XP Testing

Correct Answer

Explanation

Why Customer Involvement in Testing Is Difficult

Correct Answer

Explanation

Automated Testing Frameworks

Correct Answer

Explanation

Three Reasons Test-First Doesn't Guarantee Thorough Testing

Correct Answer

Explanation

New Build Acceptance Rule

Correct Answer

Explanation

Story Cards, Tasks, and Test Cases

Correct Answer

Explanation

Tests Must Pass After Integration

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: