Home > Articles > Software Development & Management > Agile

ATDD as a Third-Level XP Practice

Markus Gärtner, author of ATDD by Example: A Practical Guide to Acceptance Test-Driven Development, tears apart different levels of working with acceptance tests. He takes a closer look at the technical origins of Agile software development in the practices of extreme programming, and outlines a gradual line of improvement for teams working with ATDD.
Like this article? We recommend

In the second edition of his book Extreme Programming Explained: Embrace Change, Kent Beck distinguishes between primary and corollary practices in extreme programming. [1] Among the primary practices, Beck lists pair programming, the informative workspace, and a 10-minute build. Among the corollary practices, he mentions incremental deployment, a single codebase, daily deployments, and so on. Beck explains that he learned between the first and second editions of Extreme Programming Explained that teams won't be able to implement the corollary practices until they have some of the primary practices in place. For example, without a 10-minute build, daily deployment becomes impossible. Without pair programming, continuous integration, and test-first programming, practices such as shared code, code and tests, and a single codebase become a nightmare.

While I was writing and implementing the acceptance test-driven development (ATDD) examples for ATDD by Example: A Practical Guide to Acceptance Test-Driven Development, [2] I assumed that teams can work with automated acceptance tests on multiple levels. I don't claim that I invented any of these tests. In fact, I recently read a 2005 German book, Testgetriebene Entwicklung mit JUnit und FIT: Wie Software änderbar bleibt (Test-Driven Development with JUnit and FIT: How Software Stays Changeable), [3] in which author Frank Westphal combined then-current ideas about mock objects and outside-in development. Those ideas led to Steve Freeman and Nat Pryce's 2009 book Growing Object-Oriented Software, Guided by Tests. [4] In another 2005 book, Fit for Developing Software: Framework for Integrated Tests, [5] Rick Mugridge and Ward Cunningham wrote about ATDD and collaboration across all the roles in a project. So, in fact, the ATDD approach is quite old.

Having seen how all these different people apply test-driven development in one way or another, it occurred to me that a similarity exists between the application of ATDD and Kent Beck's primary and corollary XP practices. Teams can gain the biggest benefits by starting with the involvement of a real customer. This refers back to specification workshops, where ideally a customer talks with us about upcoming features for our products. The next step for most teams lies in automating the examples that they and their customer identified in the workshops. At first, automation might follow this process; however, if the team improves its process continually, over time they should be able to develop tests and functionality in parallel. I've rarely seen a working outside-in development approach put into practice. However, if the team achieves collaboration across all roles involved, they can develop the software based on the high-level examples from their customers. Let's take a closer look at these three different parts of the process—specification workshops, automated functional tests, and outside-in development—and relate them to the primary and corollary practices of XP.

Specification Workshops

Kent Beck lists real-customer involvement as part of the corollary practices. Yet teams that are new to Agile processes often struggle with customer collaboration. Without a whole team sitting together in its informative workspace, getting real customer buy-in becomes a difficult duty. I work with teams from their first day to get in touch with the business side. One of the main advantages of this approach becomes apparent when the team delivers working, useful software to the customer for the first time. With every new on-time delivery, a trusted relationship is fostered. I think this practice is crucial in software development.

XP describes the role of the onsite customer. The idea is that a customer is in the same room with the team, working closely with the team on a daily basis. Scrum talks about the role of the ProductOwner in this regard; the ProductOwner should be available to the team at least 50% of the time. With such direct collaboration, teams avoid playing the children's game of "telephone," and they can implement software that really enlightens its users.

Specification workshops should involve the whole development team, or at least every special role should be part of it. At minimum, the "three amigos"—the ProductOwner, a programmer, and a tester—should attend. [6] On a basic level, you can hold specification workshops after forming your whole team. Specification workshops then become a corollary practice to the whole team practice from XP.

In the light of real-customer involvement, however, specification workshops might also be one step further away. Without real-customer involvement, it will be hard to derive and trawl the requirements for the upcoming features. While the ProductOwner or onsite customer can help the team as a customer proxy, the tacit knowledge from real users will be distorted—like messages becoming lost in translation among kids in the telephone game. On the other hand, if the team manages to involve a real customer, a real user, or a real stakeholder of their product into their specification workshops, then the workshops as a practice become a corollary to XP's real-customer involvement. I recommend at least starting to work on this relationship early with real users.

So specification workshops might be both first-level and second-level practices, in relationship to the workshops Beck mentions in his second edition of Extreme Programming Explained. But there is certainly more to ATDD than just specification workshops. Let's consider another aspect.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020