- Understand what testing is and why it is important
- Learn a few of the various types of tests
- Recognize the importance of Test Driven Development (TDD)
- Understand the red/green testing workflow
- Gain the ability to read and write tests
TDDTest Driven Development / Design
AssertionAn expression containing some testable logic
Assertion LibraryA package of assertion functionality. Usually distinct from a
Testing Framework. Chai is an example.
Testing FrameworkA library that determines how tests are organized and executed. Mocha is an example.
Red/Green Testing- a workflow for testing your code, in which we write and fail tests (red) before we write any implementation code to pass the test (green)
Unit TestA test that tests one function or one object in isolation to make sure that it behaves the way we were expecting it to behave
Integration testA test that tests the interaction between two units to make sure that they play together nicely and work the way we expect them to work.
Strategies, Tools, and Functions
On Your Own Open this repository, then:
- Read the README, and follow the
- Run the
npm testcommand in your terminal and explore at the result.
- Open up the
functions-test.jsfile, and read every line, using all of the terms of art that you can.
Discuss With Your Group:
- What do you notice about this file? What does it seem like this file is doing?
- Which pieces of code are clear in their purpose? What is unclear?
- What sort of functionality is being tested?
What does it mean to test your code?
We’re always testing our code. We pull it up in the browser and poke at it. Does it do the thing we were expecting it to do? Yes? Then the code works. It’s time to go and celebrate. No? Well then, back to the drawing board, right?
For small code bases, this works. Write or change some code and then flip over to the browser and check to see if you got the desired result. The problem is that this doesn’t scale very well. When our applications start getting big, we end up with more and more places to poke.
Even worse: we can end up in a situation where changing code in one place causes something to break somewhere else—somewhere that we’re not currently poking.
Constantly poking at our code manually is tedious and it’s not the best use of our time. We’re better off writing some code that tests our other code for us. It’s a really efficient way to maintain quality in our code base.
The bulk of your tests for an application are likely to be unit tests. Unit tests test one function or one object in isolation to make sure that it behaves the way we were expecting it to behave. The bulk of your tests for an application are likely to be unit tests (both at Turing and in the work environment).
Integration tests test the interaction between two units to make sure that they play together nicely and work the way we expect them to work. You will get many opportunities to experiment with this type of test at Turing (including Mod 1) and in the work environment as well.
Benefits of Testing
- Unit & Integration tests are a safety net that helps developers find software bugs early
- Unit & Integration tests provide documentation by telling a living story about your application
- Unit tests foster simplicity by forcing you to write code that is decoupled, flexible, and configurable
- Integration tests allow us to be confident that all those small pieces are working together as expected
- Tests can prevent users from breaking your application (example: think about a website that auctions off items like EBay. What happens if a user tries to bid on an item that has already been sold? Are they able to? Does the app break or do they get a nice error page?) Testing helps plan for error states.
Think - Pair - Share
Consider an application that you use regularly.
- What is one piece of functionality that you could test from your application?
- Would that be a unit or integration test? Why?
- What would the consequences for the company be if this piece of functionality broke?
What is Test-Driven Development?
Test-Driven Development (TDD) is one of those things that is deceptively simple to explain and incredibly hard to do. The basic premise is that we write our test for a piece of required functionality before writing any implementation code.
Ideally, we’d follow Red/Green Testing. This means we would write the test, then fail the test, and then finally write the code to pass the test. Once the test passes, you can then safely refactor your code to optimize your solution.
- What’s the purpose of failing the test before we write the code to pass the test?
The Testing Cycle
One important thing to note is that TDD is not about writing tests. Writing tests is writing tests, period. TDD is more than that - it’s a methodology in which three activities are tightly interwoven: testing (in the form of unit testing), coding, and design (in the form of refactoring). In order to do TDD well, you should follow the following steps:
- Think and write test cases - this step ensures that you understand the functionality that is required
- Red – In this step, you try to run your test. You have no implementation code, so your test should fail.
- Green – Write the minimum code required to get the test to pass
- Green – Ensure that no old tests fail.
- Refactor - Refactor to ensure functionality is intact and the code is refined.
- Repeat this cycle - Steps 1 - 5 are repeated multiple times so that all the features are covered in TDD cycles
In Your Notebook
- What is your understanding of why testing is important?
- Explain the steps of TDD in your own words.
What happens if you don’t test first?
“I’ll write tests later. I just want to get this working first,” is one of the greatest lies in software development and it’s usually one that we tell ourselves.
Beyond the issue of general motivation — let’s face it, you’re never going to go back and add those tests — there is the issue that not all code is testable. We won’t run into this issue today, but we will soon. The thing you want to keep in mind is that if you write your tests first, it’s really hard to find yourself in this situation.
Steve’s Law of Testing: If something is hard to test, it’s probably not your test’s fault.
Mocha and Chai
In Mod 1, we will be using the Mocha testing framework along with the assertion library Chai.
Mocha is a testing framework that runs on
Node.jsin your terminal. This is what allows us to organize and execute our tests.
Chai is an assertion library that plugs into Mocha. The assertion library is what actually runs the specs and determines whether any given condition is valid or not.
When we ran
npm install we brought Mocha and Chai into the first-unit-tests warm up repo! You’ll learn about
npm in depth in M2, but for now it allows us to install packages like Mocha and Chai.
You won’t need to run this every time, just when you initially clone a new repo that utilizes packages.
When we are testing code, it’s usually best to have the implementation code pulled up, as well as the test file. You’ll constantly be going back and forth between the two, and need to compare what is in each, so this will make you much more effiecient.
implementationfile refers to the code we are actually testing.
testfile will be the automated tests that we write, that verify our class or functions do what they should.
- It is important to keep scope in mind: variables declared in the
testfile are not available in the
Eventually, we’ll be writing our own tests, but for now we’ll start with some prewritten tests. This allows us to see the process, and get some practice reading error messages
Head over to that same repository and begin to folow the TDD workflow - fail the tests, then write the code to pass ‘em!
In your journal or notebook, reflect on the following:
- What are the benefits to testing your code?
- What is the Red/Green testing workflow? Why do we use this process?
- What is Mocha? What is Chai? Write an example of the code that comes from Chai.