Hopefully, you wrote those other view tests.

I know testing can be hard at first, but once you write a few,

it becomes a lot easier.

Tests generally follow the same patterns, too.

So once you've written tests for one app, writing them for

another app is a lot more obvious.

We've tested our models, we've tested our views, and our URLs.

Now let's test our templates.

There won't be a lot to test here, but

it's good to make sure that our templates work like we're expecting them to.

First though let's look at how I wrote those other view tests.

Which, there we go.

I think we can get them all on screen there.

So this is the one we wrote earlier, the course_list_view.

And then there's the course_detail_view.

And the step_detail.

I suppose I should've called that view, as well.

So, let's look at each of these.

The weirdest part in these is probably the kwargs.

And, maybe the assertEqual.

So, when we're trying to get courses detail.

We have to pass it some kwargs for the URL.

And, we have to say kwargs.

And then, we give it the pk and this.

There's another way of doing it.

Where you do like that and then in here is where you put the kwargs.

I find that less explicit and I don't like doing it that way.

I find it much easier to just do it this way and not have to worry about it.

So anyway, that's how we use reverse there.

And here, same idea but we have to do course_pk and step_pk.

And then, like I said, this is different.

We have assertIn and we have this courses object.

And we know course is gonna be a query set or a list, effectively.

On the two detail ones, we don't get that.

We get a single object.

So, we make sure that course is equal to whatever's in our context as course,

or that our step is equal to whatever is in our context as step.

So it's a little bit different.

We have to pay attention to what that object is.

And really, though, that's fine.

But now though, let's use these views to test our templates.

So we'll make sure that our templates are getting the right templates.

We're gonna use two new assertions here.

We're gonna use the assert contains, and

we're gonna use the assert template used assertions.

So first, let's update our course list view test,

to make sure that we're using the template that we want.

So self.assertTemplateUsed.

And we're gonna make sure that response, R-E-S-P,

used courses/course_list.html.

Now, the template used can be anywhere in the stack of templates, so

we could check to make sure that it used the layout template if we wanted, so

that we know it's like, hey, it's fetching this layout template.

It's just anywhere in that stack of templates.

This should be a fairly, somewhat obvious, assertion.

And let's also make sure that

the name of the first course is printed out somewhere on the page.

So we're going to do self.assertContains.

And we're gonna make sure that the response contains self.course.title.

Now, we don't want to provide any of the surrounding HTML,

because that might change.

We don't want to have to update our tests just because we changed some HTML, or

our design team changed some HTML.

or whatever.

So assertContains, make sure that the final rendered output of the template,

the text that comes back in the response, goes back to the browser or

the client, has whatever string we've passed into it.

And in this case, we're making sure that the name of our course,

the title of our course, is somewhere on the page.

Now, you have to be a little careful with this one to make sure

that whatever you're looking for

isn't something that's going to pop up in the standard, like, HTML or something.

Like looking for each one, or doc type,

is often really tricky because, you know where those are going to show up, right.

Okay, so let's look and see if all of our tests pass.

Cool.

All five tests passed.

That's great.

That means that our project is fairly well tested.

Great work.

At this point, you should feel pretty good about adding similar template assertions

to both of the other view tests.

You go ahead and do that, and I'll be right back with one last surprise.