All right.
Time to do some manual testing here.
What we're going to do is use postmen to manually create a ticket and then manually update it.
So I've still got postman open right here inside a postman.
The first thing we're going to do is make sure that we are still signed in to make sure that you're
still authenticated.
You can make a GET request to API users current user so when I send this off I see that I am logged
in because there is an object right there.
If you are not logged in it will say current user no instead to log back in.
You can open up another tab inside a postman.
You'll want to make a post request to API users sign up make sure you've got body raw Jason selected
and then just enter in an email and password as soon as you sign up with an account you will then be
considered to be authenticated.
So come back over to this tab where you're checking your current user status send the request off and
just make sure that you are signed in then finally will open up a third tab and inside of this third
tab we're going to make a post request to API slash tickets we'll make sure we've got raw and Jason
selected and we'll enter in some attributes for a ticket.
So a title and a price once I've got that and I'll then send the request off and I should see something
that says status to a one create a down here and I should see some attributes around the ticket as well.
And now hopefully most critically we should be go back be able to go back over toward terminal and see
some logging information around not only publishing and event but also receiving end event as well.
So you'll notice that I get event published to ticket created that's for my ticket service and then
for my order service I see message received on the subject of ticket created.
And it was received by the orders service
that's our ticket created events.
Let's make sure that ticket updated works as well.
So to do a updates we're going to once again on this tab where we just created a ticket.
We're gonna grab the idea right there.
The ticket we just created and we'll make a request to API tickets Slash.
And then the idea of the ticket you just created will then adjust the price in some way dollar adjust
my price to say about 10 instead I'll then send the request off we should once again get a status of
two hundred OK and then see the updated record right here.
And I've got a price of 10 very good.
Now again as the real test back over to our terminal and we should see something that says even published
you ticket updated and message received on ticket updated you will notice that the console logs here
are out of order.
That is only ok just because of the way scaffold works.
Sometimes these console logs get reflected in a slightly different order.
No problem whatsoever.
At the end of the day the order service does not somehow magically predicting that this event is going
to come over before it does.
All right.
Let's say that this is a good manual test.
However has I mentioned this is where all those concurrency issues are going to start to become absolute
first class citizens problems so we're gonna have to solve now that we've got this entire publisher
and listener infrastructure setup to two pause right here.
We're going to start to see some really weird behavior in the next video.