I'm going to copy the should return 404 test case for the should return 404 if todo not found test, and we're going to paste that into the exact same test for the delete route, and all we have to do is change .get to .delete, and save the file. This is going to rerun the test suite, and now we have two tests under delete; they are both passing:

You can see our last test still fails, so we can go ahead and do the same thing. I'm going to copy the code from should return 404 for non-object ids, which verifies that non-ObjectIDs cause a 404 status code. I'm going to paste it in the last test case, changing the .get method call to .delete. If I save the file it's going to rerun the test suite and this time around all 9 test cases are passing:

With this in place, we now have DELETE /todos tested. Let's go ahead and wrap this one up by making a commit over inside of the Terminal.

I'm going to run git status to see what changes I have going on. We made one small change to the server file and we added our tests to the server.test file. I can use git commit with the -am flag to make it commit, and a good message for this one would be Test the DELETE /todos/:id route:

git commit -am 'Test the DELETE /todos/:id route'

I'm going to take that commit and push it up to GitHub, and there's no need to deploy to Heroku since we haven't created anything visually different. We did tweak the server code just a little bit, but we'll worry about that a little bit later. For now, everything is good; we can move on to the next section where you are going to create the final route for managing Todos. This is going to be a route that lets you update a Todo.