Home > Articles > Programming > Java

  • Print
  • + Share This
Like this article? We recommend

Getting Started

The next morning, John and I paired together at one computer and began work. The first thing we did was model the first feature we needed to develop, breaking it down according to how we might test it. Once we had decided where to begin, we went over the integrated development environment (IDE), because the automated unit tests developed in TDD are usually written in the same language as the application code. John had prepared a demo for me, using an application that was familiar to both of us. He showed me how to run the automated unit tests from within the IDE. In this particular program, we could run a suite of automated unit tests, or we could run them individually by highlighting the test in the text editor and pressing a hotkey combination. Once I was familiar with the IDE, we began to write a test.

The IDE incorporated the xUnit test framework for us; all we had to do at this point was write code for an assertion. (Ron Jeffries says, "An assertion is a program statement that states what should be the case at that point in the program.") We started to translate my testing idea on the area where we needed to start coding, but soon hit a problem: My test was too complex. John helped me to design a simpler test, but it felt almost trivial to me. He explained that we needed to start with a test, and we would write more powerful tests as the design worked itself out. For now, we needed to start with a simple test that would call a method and then evaluate the result by using an assertion. We wrote the test code, and John stubbed in a name for the method that we hadn’t written yet. He then ran the test, and our xUnit tool in the IDE displayed exactly what we were looking for: a "red bar," meaning that the test had failed. This was correct behavior. The error message stated that the method we were calling was unknown.

Now it was time to move to the next step: creating that missing method, the real production code that we would be using in the program.

This procedure felt a little backward to me at first, but working with John soon made it seem smooth. We wrote a method using the name we had supplied the test case, and ran the test again. We got a red bar again, but it wasn’t due to nonexistence of the method; it was due to the assertion failing because we didn’t yet have the code to satisfy the assertion. So we went back to the code, filled in the method to satisfy the assertion, and reran the test. Now we had a green bar. Victory!

Now I started driving, and I ran the test and got the green bar. I changed the data in the automated unit test and reran it. John then taught me a little trick: He had me do another assertion that was identical, but did the opposite of the first test. For example, if you had a first test doing an assert true, you would pair it with an assert false. He said it was a good practice to try once in a while during development, that sometimes an assertion would work because your method was returning something misinterpreted by the framework.

Once I was comfortable with what I’d worked on so far, we wrote a new class and related methods. We decided on a simple test for a method we would eventually need to write—reading in values, evaluating them, and returning a result. I dove in with confidence, had the IDE generate the xUnit automated unit test framework code for me, and decided what kind of assertion to use. As I was typing, though, I began to freeze up. What would I name this method that I hadn’t written yet? I hit a mental block trying to think of a name for the method. John knew I was struggling and asked what was up. When I explained what I was grappling with, he said to just call it whatever came to mind; we would change the name later anyway, using the refactoring functionality of the IDE. He said that this was standard practice anyway; as the design tightened up, we would find our first choice would often be wrong. I named my to-be-developed method foo, and wrote an assertion that looked something like this:


I hadn’t written method foo yet, but knew that it needed to take two values, sum them, and return the result. The test code above reads like this: "Assert that the value returned from method foo is equal to 900 when I tell it to total 500 and 400." If this assertion fails, I either haven’t written the code to do it yet, or there’s a problem in my method.

This wasn’t easy to do at first. I struggled with thinking of how I would call code I hadn’t written yet, and then how I would test it with something tangible. We knew that the method would get more complex as we went on, but we needed to start coding and this was a simple place to start. I ran the test, it failed, we added the code to satisfy the assertion, and then added another assertion that looked something like this:


It was the opposite of the earlier assertion. It would not evaluate to zero, so it passed as well, and we were on track. We enhanced the tests to fit our design requirement for that method. We altered it to use variables populated with test data instead of hard-coded values, and we used setup and teardown methods to prepare and clean up the test data prior to and after each test run.

Now that the code behaved the way we needed it to behave and we had a handful of tests, we renamed the method I had struggled with naming. At this point, we had an idea for a better name than foo, so we opened a refactoring browser window and told the IDE to rename all instances of foo to our new method name, calculate_bonus.

In the past, when I had to do a method rename after a couple of hours of development, I would use find/replace and then run a few ad hoc unit tests, hoping that I hadn’t broken anything. Sometimes I might miss an instance. But now I saw a useful side effect of test-driven development: automated regression tests. Once John and I renamed our method, we reran our tests. The resulting green bar told us that we could move forward with confidence. Renaming the method didn’t cause any failures, so we knew that we hadn’t injected a bug in the renaming process. A suite of tests tested the method directly, along with other methods that called it. At the press of a button, the green bar and the passing tests it represented gave me a lot of confidence.

I now realized through experience how our test cases not only drove the design but served as a safety net for refactoring. This was something I had understood from working closely with TDD developers in the past, but until I experienced it firsthand on software I was helping to write, I didn’t fully grasp the power of the technique. John explained that he had had a similar watershed moment when he learned to program in a procedural language. After trying object-oriented (OO) programming for a while, he had a moment where he really felt he understood it. When he tried to do procedural programming again, he found it difficult at first because he now thought of programming in OO terms. After moving to TDD, practicing the techniques, and finally getting TDD at last, he said he had trouble programming in any other way. He now feared programming without tests because not only did the tests help drive the design, but they gave him much more confidence in the code he was developing. He wasn’t the only developer who mentioned being fearful of not having automated unit tests in place when developing software.

  • + Share This
  • 🔖 Save To Your Account

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