Home > Articles > Software Development & Management > Agile

The Future of Agile Software Testing with xUnit And Beyond: An Interview with Gerard Meszaros

Gerard Meszaros wrote the groundbreaking book, "xUnit Test Patterns." Matt Heusser followed up with one simple question: What's next? Meszaros discusses how unit testing is different than traditional, black-box testing; the limitations of test patterns; and how the programming language chosen affects testing.
Like this article? We recommend

Gerard Meszaros is an Agile software development consultant, trainer, author and occasional conference speaker. His book, xUnit Test Patterns: Refactoring Test Code is a recent Jolt award winner and is becoming a standard reference on the subject of unit testing. Gerard will be speaking at the Agile 2009 conference with a session on "From Concept to Backlog," covering the fuzzy front end of software projects. We interviewed Gerard just before the conference on how the book developed, where the patterns can be applied, and his view of the future of testing and Agile.

Matt Heusser: Obviously you have a background in programming and testing. Tell us a little more about where you've been, and how that brought you to write xUnit Test Patterns.

Gerard Meszaros: My background is as a developer, project manager, and software architect building large telecom systems. I was involved in reviewing the original Design Patterns (Gamma et al) and the first patterns conference (PLoP) in the mid 1990s. I also lived through the transition from ad hoc object-oriented methods to UML and RUP, and it seemed like it was getting harder and harder to develop all the artifacts (and teach others how to do it).

I knew Kent Beck from the patterns community and laughed when he first said he was doing “extreme programming.” As an architect, it seemed completely anathema to everything I valued. But in deeper discussions with Kent, I saw that our values were the same. This led me to investigate further how to apply the ideas.

Matt: Why test patterns?

Gerard: There is plenty of literature on design patterns for production code. As I wrote in the preface of my book, I started doing extreme programming (XP) and test-driven development (TDD) in the late 90s; I found that how we wrote the tests had a huge bearing on how much they helped (or hindered) rapid development.

We were really on the bleeding edge in those days so there weren’t a lot of resources available to help us. We compared notes at the early Agile/XP conferences and found that a lot of us were landing on more or less the same techniques to address the issues.

xUnit Test Patterns is the book I wish I had when I was starting out. I’ve been very gratified by other practitioners saying exactly the same thing when they reviewed the book.

Matt: How is unit testing different than traditional, black-box testing? Do you think developers could stand to benefit from the traditional black-box test list (such as bounds and equivalence classes)?

Gerard: In some ways, it is very similar and in others it is quite different. We use a lot of the standard test techniques to identify the tests that we need. But we write the tests for a very different purpose.

I think of the automated unit tests (and automated story tests) as “bug repellent” rather than “bug detection.” Traditional testing is about finding bugs while automated unit testing, done in conjunction with Test-Driven Development, is all about preventing the bugs from happening.

Matt: Likewise, are xUnit test patterns also transportable to business-facing level of testing? What about load, performance, and exploratory testing?

Gerard: Yes, testers like Lisa Crispin reviewed my book and told me that they found it useful when designing their business-facing tests.

Regarding the other kinds of tests: A lot of the techniques I describe can be applied to para-functional tests such as load and performance testing. Exploratory testing by definition cannot be fully automated but testers doing exploratory testing can use automated test tools or scripts to help them execute the tests they define on the fly.

Matt: Where do you see limitations of the test patterns? Which code do you refuse to test? That is, do you see unit tests having a place for developers using more bare-metal tools like shell-scripts, or assembler code?

Gerard: All techniques have limitations, especially when they are abused or overused. The biggest hazard with automated unit testing is writing tests that are hard to understand and which are therefore hard to maintain as you evolve the code. A lot of the techniques I describe are ways to avoid this issue.

As for using TDD and automated unit tests in bare-metal tools like C, the higher the overhead of debugging, the more benefit there is to doing TDD because preventing mistakes (also known as bugs) saves even more effort. One area particularly ripe for the application of TDD is embedded software. Developers can save a lot of effort by removing most of the bugs while working in an IDE so that when they deploy the code into the hardware the only bugs left are ones related to integration, not basic logic errors. This requires building some test infrastructure and layering in the software properly to allow stubbing out of the actual hardware interfaces -- but the payback is huge.

Matt: Does unit testing change when you shift paradigms? For example, should C code be unit tested differently than Java? And if so, how?

Gerard: Yes, C should be tested even more thoroughly than Java or C# because the compiler won’t catch as many mistakes! Likewise for dynamic scripting languages like Ruby or Perl; it is easy to introduce bugs that will only be found at runtime, so running all the code regularly via automated tests is crucial.

Matt: What measures and metrics do you think are appropriate for developer tests?

Gerard: When doing TDD, statement coverage of the code being tested should be very high, ideally 100%. I’m not a metrics guy but I would suspect that test code should have a very low Cyclomatic Complexity metric because it should contain very little conditional logic. To me, the ultimate measure of the quality of the test code is how easy it is to read, because it will be read a lot!

Matt: In the past, we've heard a lot of confusing terms. Unit tests, acceptance, system, integration ... how do you slice and dice your definitions of tests?

Gerard: Terminology is always an issue. There is no single definition we can all agree on for many of these terms. Trying to standardize the terminology is one of the reasons why I wrote the book, but not every agrees on the need to have agreement on crisp definitions. Personally, I subdivide tests based on the kinds of characteristics we are verifying (functionality, para-functional qualities) and the granularity of the system under test. So I have functional unit tests, component tests, system tests, and workflow/integration tests. Acceptance tests and regression tests are just two particular uses of any one tests at different points in the lifecycle of the code.

Matt: What attracts you to Agile 2009 over other conferences?

Gerard: I get to get back together with many of the other thought leaders in the Agile space and we can compare notes on what we have learned in the past year. Most everyone who’s anyone is there.

Matt: And what will you be speaking about?

Gerard: I’m giving a tutorial on xUnit Test Patterns (of course!) as well as one called From Concept to Backlog. The latter describes the overall process between when a business person gets an idea for how to make or save money with software and when they show up in the team room with a stack of story cards and a wad of cash (the budget). Most Agile methods ignore this part of the project, so there is a lot of confusion and mythology about what should or should not happen in this very important time period. As a result, a lot of projects involving people new to Agile really flounder in the early stages. This can be prevented by some appropriate planning and activities. And no, planning is not banned by Agile!

Matt: How do you see the future of testing tools and test automation frameworks such as FitNesse and Concordion?

Gerard: I think we are in the middle of a major growth spurt for these tools and new competitors like Cucumber. Storytest-Driven Development (or Acceptance Test-Driven or Example-Driven) is a key success factor in Agile projects. We are finally getting some tools that provide decent support for the process.

Of course, there is still a lot of room for improvement, and the various tools are pushing each other to get better -- which is great!

Matt: What do you think are the next steps that the Agile movement will take in the next few years?

Gerard: If I were good at predicting the future I’d be rich playing the stock market or the horses -- or would be a hugely successful waterfall project manager! Since I’m neither of these, all I’m prepared to say is that I suspect we’ll see continued refinement of our understanding of what makes Agile software development effective.

Part of this is the mixing in of lean concepts such as Pull, Flow, and Waste Reduction. Personally, I have been pushing hard the incorporation of UxD (User/Usage centered Design) practices into the Agile process; I think we’ll see a lot more of this. I see that one of the conference keynotes is by a UxD person (Jared Spool), which is great.

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