Home > Articles > Programming

Quality Code through Software Testing: Where Do I Start?

📄 Contents

  1. An Approach to Testing
  2. The Recipe
This chapter from Quality Code provides a reasoned approach to testing and clears away some of the questions about testing strategy so that testing techniques can be used effectively.
This chapter is from the book

Knowing how to approach a problem and having a plan of attack simplifies and increases the effectiveness of testing. In this sense, test-driven development provides an easier framework in which to test because your tests are directed by what you want to implement next. Untested existing code presents a more formidable challenge because there are so many options for how to start.

This chapter provides guidance in the form of a reasoned approach to testing. The strategy is not radical or new, but it establishes a context in which the techniques in the remainder of the book can be applied. It hopefully clears away some of the questions about testing strategy so that testing techniques can be used effectively.

This chapter—in fact, this whole book—focuses on automated testing. In the Agile Testing Quadrants identified by Lisa Crispin and Janet Gregory [AT], it is all about Q1 and Q2, the quadrants that support the team.

An Approach to Testing

No one has discovered the magic formula for perfect testing. This means that, as practitioners, we need to apply a combination of reasoning, experience, and intuition when we write tests. This section captures many of the concerns you need to consider when writing automated tests.

Understand Your Scope

The first question you need to ask yourself is, “What am I trying to test?” This broad question includes the need to answer several more detailed questions, such as the following.

  • Which use cases am I trying to verify?
  • Are you trying to test the full stack, an integrated subset, or a unit?
  • What technologies are you trying to verify?
  • What architectural layers are you trying to verify?
  • Are you testing new code, clean, well-written code, or are you rescuing a legacy hair ball?
  • Can you decompose the testing problem into usefully smaller, more tractable pieces?

A full stack test gives you the ultimate verification of the fully integrated system, but at a cost. Full stack tests often run slowly due to the presence of all of the component interactions, including network, database, and file system. Full stack tests often have difficulty distinguishing nuanced behaviors and can require complicated recipes to induce error conditions because of the larger number of conditions that you must manage to achieve those results. Finally, full stack tests may be fragile or difficult to implement because of user interface and timing interactions. The smaller the scope of the test you tackle, the less these factors will have significance.

The technologies and architectural layers will naturally relate to your scope, but will steer the testing tools you use and influence your options for test doubles.1 The testing frameworks you use to test a web interface are different from those for a ReST service, which are different from those for a Java class. Targeting the business layer may give you substitution options for the database, whereas testing stored procedures or ORM mappings may not.

The maturity and cleanliness of the code will guide your approach significantly. If you are starting a new project, you have the power to create the future. An existing exemplary code base makes your life easy, perhaps even boring, as you focus on the task at hand instead of reverse engineering and debugging. An unfamiliar spaghetti mess requires patience, insight, and a host of techniques from Michael Feathers [WEwLC]—such as characterization testing and seam2 identification—before you can even start cleaning it up and adding features to it with confidence.

The more independent the parts of your system, the more likely you will feel confident testing those parts separately. Just like system decomposition, breaking your testing task into multiple subtasks will simplify your work and reduce your overall coupling.

A Conceptual Framework for Testing

For conceptual guidance, I use two principles to guide the overall shape of my testing efforts. First and foremost, I focus on the purpose of the software I am testing. Second, I actively work to reduce the degree of coupling introduced by the tests. Let’s consider purpose now; we will discuss coupling in the next chapter.

The purpose of code applies differently at different levels. At a system level, the purpose of the code is the reason the software exists: its features, requirements, and use cases. Critical evaluation of the purpose helps to constrain your test cases and acceptance criteria. Is it important that a user interface element is a particular color or size or that it is aligned a particular way? You may not need to verify particular database fields if the value of the application is simply that the data or state is persisted and can be retrieved; exercising the retrieval and verifying the results may be sufficient.

At a module or component level, purpose refers to a function in the overall system. Integration tests satisfy the needs at this level. A module may overtly implement a feature, directly bearing the responsibility for the functionality the users expect. Alternatively, a module may implement an underlying, enabling design component. Either way, the module serves a role in the overall system. That role should be clear, and it needs to be tested.

At a unit- or isolation-test level, I like to think of the purpose as the value added by the code. Those who live in countries like Mexico or the European Union with a value-added tax (VAT) may find this concept clear. A company only pays a VAT on the amount of value it adds to a product. Raw materials or component parts have a value when you receive them that is subtracted out of the value of the product you sell for purpose of taxation. Similarly, your code takes the libraries and collaborators on which it is built and adds an additional level of functionality or purpose for its consumers: the value added by that code.

Defining a unit test has caused considerable debate, but the value-added perspective gives us an alternative. Many have used definitions like that put forth by Michael Feathers3 stating what a unit test does not do. I feel this merely codifies some test-design heuristics as rules and prefer to use the value-added concept for an inclusive definition of a unit test.

  • A unit test is a test that verifies the value added by the code under test. Any use of independently testable collaborators is simply a matter of convenience.

With this definition, use of an untestable method in the same class falls within the value added by the code under test. A testable method called from the code under test should have independent tests and therefore need not be part of the verification except to the extent that it adds value to the code under test. Use of other classes can be mocked, stubbed, or otherwise test doubled because they are independently testable. You can use databases, networks, or file systems at the expense of test performance, although I would not recommend it.

Every subset of the system, from the smallest method to the entire system itself, should have a well-defined purpose. If you find yourself struggling to test the subset, you may not know its purpose. If you do not know the purpose of the subset, it probably has some implementation, design, or architectural issues. You have just diagnosed current or future problems maintaining and extending your software simply by looking at it through a particular lens in order to test it.

State and Behavioral Testing

Classifying the testing task at hand aids in identifying the best approach in writing the tests. Determining whether a test will verify state or behavior usefully steers the testing process.

Pure state verification exercises the code and examines the resulting changes in data values associated with the operation. Mathematical functions that simply transform inputs to outputs exemplify the target of state verification. In a functional model, verification simply determines that the return values correlate correctly with the input parameters. In an object-oriented model, you additionally verify that the attributes of the object have changed (or not changed!) appropriately. State verification tests typically supply inputs and verify that the outputs correspond to the inputs in the expected ways.

Behavior verification checks that the code under test performs the right operations: It exhibits the right behavior in ways that go beyond data transformation. The purest example of behavioral verification simply orchestrates activities, as in Listing 3-1. It is the method that only calls other methods that are independently testable in order to coordinate their execution order and to channel the outputs of one to the inputs of another. Behavioral testing relies heavily on test doubles, frequently mocks.

Listing 3-1: A JavaScript example of a purely behavioral function using the jQuery.Deferred() implementation of the Promise pattern to coordinate asynchronous computation. It orchestrates the steps of the process, ensuring that dependencies are satisfied and parallel tasks are coordinated, but does no computation itself.

function submitTestScore() {
    computeScore(), // Returns deferred object
    allocateAttemptID() // Server call returns deferred object

Highly decomposed software tends to be either behavioral or stateful. You will encounter cases that justifiably do a little of both, but the majority of the software you test will fit cleanly into one category or the other, guiding you toward the most effective style for testing it.

To Test or Not to Test

Although most of this book assumes you want or need to test your software, you should not blindly assume that is necessary. Perhaps counterintuitively, the primary purpose of automated tests is not to verify new functionality. After you create the test, each time it runs it mainly serves to verify that you did not break existing functionality.

But what if you do not care about preserving functionality? If you write code that will be thrown away, consider whether you should write automated tests for it. Prototypes, proofs of concept, demos, and experiments may all have short and limited lives.

On the other hand, code that you want to sustain should be tested. If you test your code properly, you will increase your ability to modify your code safely. Code that you expect to base your business on and code that you want other people to use should be developed sustainably. This also means that the throwaway code just mentioned should be brought or rewritten under test if you decide to productize it.

You also need to decide how to test your code, and economics play a role in that decision. System and integration tests are usually cheaper and easier for highly coupled, low-quality code that changes infrequently. You will get more benefit applying unit tests to loosely coupled, high-quality code that changes often. The Automated Testing Pyramid presented in Chapter 1 assumes that you want to create sustainable software, but that may not always be the case for perfectly valid economic reasons. Or you may have inherited legacy code4 that needs rescue, in which case you will wrap it in characterization tests [WEwLC]—essentially a form of system or integration test—until you can refactor it into the form more conducive to unit tests.

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