So we've made some changes to our code base, and any time you do that, it's always a good idea to
run your tests just to make sure everything still works.
So let's open a terminal and I mean the root level of my project, and I'm going to run the tests for
the entire project.
And I can do that just by going go test V for verbose run the tests in this directory and in all the
lower directories or all the directories beneath this one of those three dot means.
So let's run them and we have a fail and the fail is right here on line.
One hundred and forty eight of handlers thought go.
Let's see what that is.
So line 140 over writing to the error log from the app.
And if you recall in Maine, don't go.
We actually assigned these two logger's to our application config.
So we need to add them in our setup test for the handlers package.
And that's easy.
I just copy and paste and I have to change the equals to a sign which will work just fine.
And I'll let's run that test again.
So I'll clear the screen and I'll run the tests and everything passed.
Now this error log here can't get error from the session.
That's fine.
That's actually being generated by the line that was causing us problems before and that's fine for
right now.
We'll worry about that when we actually have our database hooked up.
So since we've added it to the setup test for handlers, let's also add it for for the setup test in
our render package.
So in here, if you recall, I didn't call it app, I called it test app, but I'll just paste it in
and change this to test app
and we'll run the tests again just to make sure they all pass and everything passes.
So that's great.
So this is something you should keep in mind any time you make a change to your code code base, it's
a really good idea to run your tests and just make sure that everything is up to date.
And if you leave it for too long, updating your test becomes a real chore.
So do it regularly.
Any time you change your code base after you think you're done, run your tests and update them as necessary.