Okay, so let's start out with a little manual test to see if it's working.

Now, we could definitely write up some JavaScript to test it out, but

there are better ways.

A super handy Chrome web app that I use to test my rest APIs is called Postman.

Installation instructions are in the teacher's notes.

Let me show you how to test your APIs.

All right, so I was reviewing the code that we just wrote and

I found a couple mistakes in the same line.

It happens, totally happens, these are mistakes, we all make them.

At the end of this extremely long line that's right here,

the very end of this, I forgot to add the final closing single quote.

Maybe you saw that when I did that.

The other thing that I forgot to do is that there's extra parameters here.

So there's username and password.

And we're not using them, but if we don't put them there,

we have a bit of a problem.

It's a different method signature, and

we're gonna end up calling the wrong thing.

So that is now set up correctly.

Okay, so we're ready to get the server running.

So let's choose Run, and we'll choose Run, and

this will create a new configuration for us called API, so we'll click that.

There we go. It says Spark has ignited.

All right, now, I'm gonna go and open up my Postman,

which you probably have installed.

We might be running different versions, so don't let that freak you out.

It's an awesome tool.

They're always adding new stuff.

So the first thing that I want you to know here about Postman

is that you can do the different types of requests.

So what we wanna do first is we wanna post so that we can add a course.

So we're gonna do a post, and we're gonna post to

localhost4567, and we're gonna post to courses.

I'm going to put an HTTP at the front of that.

So we're gonna post to the URI of courses, and this is our server, right?

It starts on 4567 as the default port.

So, then why don't we add a header,

a specific header that says content type, right?

Because remember, it's only listening to that and I accidentally sent the post.

So, content type and the value here is application/json.

Okay.

In the body, we also wanna pass the json, right?

Remember, that's what we have promised, we had said we're going to send

application json, so we're gonna right some json here.

So, we'll do the name that we wanna send.

So json is a key value and key colon, then the value that you want.

So we'll say REST API Basics and then the URL,

and then again, so if the URL's the key and the value is

http:teamtreehouse.com/Library/rest-api-b- asics, cool.

All right, so that's the body that we're gonna send up.

So let's go ahead.

So we're gonna post to courses, saying that we are application json and

that's what the body looks like.

So let's click Send.

And we can scroll to the response.

And there it is.

There is REST API Basics.

You probably have id 1.

I had just tested this before to make sure that it works.

So it has the id back.

So that's awesome.

And also notice here that is says 201 Created.

That's because we sent that status code back, cuz we're good API citizens.

Isn't that awesome?

And so now, what happens is it stores that over here.

So these are the ones that I did accidentally when I pressed Enter and

here is the good working one that we passed.

So we can make a new request.

So let's make a different one, so let's do name,

let make this will be Java basics, remember that one?

And we'll change this from rest api to be java.

And we'll click Send.

Okay, we'll scroll to the response, and boom, there's a new one.

It's got id number 3, awesome.

So, post works, and now there's two, so let's switch our request to be a GET,

right?

So now we can list all of the courses that are available.

So let's go ahead and send that GET.

And that REST API Basics, that was the one that I tested with.

Here's the two that we added, and on yours there should just be two, right?

And see how there's these hard brackets here.

See how it's showing that there is an array of these different courses.

Awesome!

And we also added a row that lets you see different IDs.

So if I said 2, it should just return the 2.

Awesome, it does.

And if I say 3, does it get the third one?

Awesome.

And what happens if we do a different idea, like what if we do 42?

Null.

Hm?

That's not great, is it?

Because it says 200 OK but it's returning a null.

It really should return a 404 not found, right?

Let's table that for now.

So, we've done our automated testing, but this is manual testing, right?

So we've done automated testing together before where we test

isolated code in small units of work.

That's unit testing.

We can take another approach, which is called functional testing.

What this does is it allows you to test the system more in a way than an end user

using your system might do things.

So let's dive into functional testing, right after this quick break.