Home > Articles > Programming

Gaining Code Confidence Through Testing

  • Print
  • + Share This
Steven Foote, author of Learning to Program, explains why testing your code is an essential stage not only in improving the code, but increasing your confidence in it. Learn why automated tests are crucial to the coding process, how to write successful unit tests, when to test your code, and more.
Like this article? We recommend

Like this article? We recommend

One of the most interesting paradoxes of programming is this: As you gain experience, the confidence you have in your code tends to decrease. This is not because a programmer's talent decreases over time. No, it is because the longer you program, the greater the quantity and variety of bugs you have seen. With more experience, programmers realize that in systems as complex as software applications, bugs are inevitable. While newer programmers are certain that their code is flawless, experienced programmers know there are flaws, and only worry how many.

The situation may seem dire, but we are not without hope. We have ways to mitigate, minimize, and even prevent bugs. Among these techniques are documentation, proper software design, and software testing. While all of these options are important, I think the most neglected among new programmers is software testing. This article will discuss how a programmer can increase code confidence through software testing.

What Is Software Testing?

For the first few years of my life as a programmer, testing was nearly indistinguishable from debugging. I tested my programs as I was building them, running them in the same way that the programs' end users were supposed to do. I tested only the feature I was building at the moment, and if something was broken I would debug and fix it. This type of software testing is called manual testing, and its value should not be underestimated. However, manual testing has a few very large holes:

  • Manual testing is slow. You can only test as fast as you can use your program.
  • Manual testing is limited. You generally test only the feature on which you are currently working—other parts of the system may break due to your changes, and those bugs will be missed.
  • Manual testing relies on your (fallible) memory. Even if you try to test your entire program after each change, you will almost certainly forget to test certain aspects of it.

Manual testing is great, but to really gain confidence in your code, you need automated testing. An automated test is a piece of software specifically designed to test your software. Generally speaking, there are two kinds of automated tests:

  • Unit tests are used to test how a single unit of your program works.
  • Integration tests are used to test how the entire program works with other systems.

In practice, a lot of automated tests lie somewhere in the spectrum between unit tests and integration tests.

All of these types of tests are important, but we will focus on unit tests in this article, because unit tests are the most fundamental automated tests. Automated tests offer some major advantages over manual testing:

  • Rapid. Automated tests are fast because the computer executes them.
  • Comprehensive. You can easily run automated tests for your entire program when you make a change, instead of just the part of the program on which you are currently working.
  • Repeatable. Once you have written a suite of automated tests, they will all be executed every time you want to run your tests. You don't have to worry about forgetting any of the tests.

Why You Need to Test

As I mentioned earlier, I spent my first few years programming without writing any automated tests. I didn't write automated tests because I realize they even existed, and I didn't really understand what use they would have. On smaller, short-term projects, the lack of tests seemed fine; I didn't even recognize the need for tests. But as the size and complexity of my software projects grew, I started to feel the pain.

On one occasion, I was releasing a new version of a Chrome extension with some great new features. Only after I had released the new version did I realize that the new features broke some of the extension's most vital functionality. I quickly fixed the bugs and released another version, only to find I had broken something else. I think I released four versions within an hour before I got the extension working correctly again. By the end of that hour, I had almost no confidence in my code. The lesson I eventually learned from experiences like this is that you should write unit tests, because they will give you the confidence to build new features, fix bugs, and release new versions of your software. Write and execute thorough tests, and you can ship with confidence.

How to Test

I think the hardest part of unit testing is figuring out how to write tests. Having never seen a unit test, I struggled to imagine what a unit test would look like. We'll walk through an example here that will show how to write tests for a simple JavaScript function, and how to use those tests to have confidence in our code as we refactor the function. We will create a remainder function, which will accept two numbers, x and y, and return the remainder of x divided by y. The first version of the remainder code is intentionally ridiculous to give us room for a refactor later:

function remainder(x, y) {
  var decimalMatch = /\d*(\.\d*)/;
  var decimal = parseFloat(decimalMatch.exec((x/y).toString())[1]);
  return Math.floor(decimal * x);

You cannot reasonably expect to test every possible input combination, even for a trivial example like this one. Instead, you should test the places where things are different–the edges. In this case, I would want a test in these situations:

  • When x and y are the same
  • When x is 0 and y is not 0
  • When y is 0 and x is not 0
  • When x or y is really large and the other isn't
  • When both x and y are really large
  • When either x or y is negative
  • When both x and y are negative

And so on. Though I have listed quite a lot of possible tests, it's not an infinite number of tests. Let's take a look at how we might write one of these tests.

// A helper function for testing the remainder function
function testRemainder(x, y, expected, description) {
  var result = remainder(x, y);
  if (remainder === expected) {
    console.log('pass: ' + description + '\n');
  } else {
    console.error('FAIL: ' + description);
    console.log('Expected the remainder of ' + x + ' divided by ' + y +
                ' to be ' + expected + ', but the result was ' + result);

// An actual test
testRemainder(13377331, 42, 37, 'A large x and small y');

Once you have written all of the tests, you can refactor the remainder function so that it is not so ridiculous:

function remainder(x, y) {
  return x % y;

After the refactor, run all your tests again. If all the tests pass, you can have confidence in your refactored code.

What to Test

You don't necessarily need to test every single aspect of your program. Testing libraries can give you a "code coverage" report, which will tell you what percentage of total lines of code have been executed with your tests. That number is useful, but even more useful is seeing exactly which lines of code have not been executed with tests. Some code does not need to be tested. Some code should not be tested. Also, just because a line of code was executed with a test does not mean that it has been properly "tested." It just means that the line of code was executed while a test was running; if the test isn't well written, the line of code may not have really been "tested."

Your tests should serve as a description of what your code is supposed to do. If any parts of your code are not actually part of the main purpose of your code, those parts don't really need to be tested. For instance, I recently had to add a special check in some of my code to find out whether a feature from another part of the system was in place. It looked something like this:

var items;
if (newFeature.isReady) {
  items = ['a', 'b', 'c', 'd'];
} else {
  items = ['a', 'b'];

The new feature was expected to be fully available within two weeks, at which point I would remove the feature check. Writing a unit test for that code would have been counterproductive because the test would not describe what the code was supposed to do, because the code was going to build the UI with some items in either case. The question was which items did not affect the functionality of the code, and therefore should not be included in the tests.

When to Test

There is a lot of discussion and debate today about when is the best time to write unit tests. Advocates of test-driven development say that you should write your tests before you write your code. Other people argue that writing tests before writing code is impractical at best and harmful to the user experience at worst, because too much focus is given to the tests instead of the application itself. In my experience, writing tests before writing code is beneficial because it can help you think through your software's design. However, I have also found that it can lead to too much time spent thinking and not enough time actually writing code. My suggestion is to write your tests sometime before you release your software, but the specific timing doesn't really matter.

Who Should Test

Different organizations handle the responsibility of software testing in different ways. In general, if you are writing code, you should at least be writing unit tests for that code. Writing good tests is one of the marks of a high-quality, mature, confident software developer.

I hope this article has given you insight into how software testing works and why investing in it is worth your time. Now go write some code—and tests!

  • + 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