Or get how workflow is looking pretty good.
But right now, it is only running tests inside of our off service.
We definitely need to make sure that we run tests inside of all of our other services as well.
There's two ways that we can implement some additional configuration to run tests inside of our other
services.
First, I got to go back to the code tab on GitHub.
You'll notice inside of here there's a new folder of dot GitHub slash workflows that is all of where
all of our different workflow configuration files get saved.
If we open up the tests, dot Yamal one, that is the workflow, we just created a moment to go.
So there are two different ways that we can make sure that we run tests and Oliver other services.
We can either add in some additional run statements to the thing so we can make sure that we run some
more commands like change into the orders directory, install dependencies and then run tests inside
there and have another line for the ticket service.
Another for expiration.
Another four payments and so on.
That is definitely one way to do it.
But that is going to make sure that we run all of our tests in series.
In other words, we're going to run all the tests for the off service first and then expiration and
then orders and then tickets and so on until it might end up taking several minutes to run all the different
tests for our project.
Well, there's technically another way that we could wire up all of these testing workflows to make
them all run in parallel.
We can create some additional workflows that also execute on the on Polle request event.
And for each of these additional workflows we can create, we'll have them change into each of our other
individual services and run tests inside them.
So essentially, for each individual service, we create a different get hub action and that's going
make sure that they all run in parallel or essentially at the same time, which is going to dramatically
speed up our testing process.
OK.
So that means we're going to go through all of our different services, create a different workflow
file for each of them.
Going to first begin by opening up or directly editing this file on GitHub, I just want to change the
name of the file and the name of the workflow step is to make sure that it's really clear that this
is a set of tests.
We're running the tests in the off service.
So click on the edit this file.
I'm going to change the name right here to s dash off.
I'll change the name of the file as well to test dash off.
I'll then commit these changes.
And then going to copy everything inside of here, and we're going to create a couple of extra files
for all of our other services that actually have tests inside them.
Again, this is to get all these different tests to run in parallel whenever we create a pull request
or merge and changes.
So inside of my workflows directory, I'll click on the workless link.
I'm going to manually create a new file.
I'll give the file a name of tests, dash orders.
Not Yamal.
And I'll paste in all the stuff that we just copied.
All then change tests off to tests orders.
And down inside this run step.
All updated to change into the orders directory instead.
I'll then go down to the bottom and commit those changes.
All right, now, really quick, one thing, one dimension here is we never actually put together any
tests inside of our expiration service.
The only other services we have to create a workflow file for besides off in orders, which we just
graded, is payments and tickets.
So we're going to create two other workflow files, one for tickets and one for payments.
Let's take care of payments first.
So again, inside my reclose directory, I'll create new file of tests.
Desh.
Payments that YAML.
Pace.
All that stuff in.
I'll change the name right there to test dash payments.
And I'll change the C.D. right there as well.
Two payments.
Go down to the bottom.
And then just one more look at another file of tests, dash tickets, dot Yamal.
Do the Paiste tests, Dasch tickets.
And then change city off into seedy tickets.
And then finally go down to the bottom and commit.
OK.
So now he should.
Whenever we create a pull request, which changes to a pillow request, run all for these jobs in parallel,
which would significantly speed up our run.
Before we test this, however, we do need to make sure that we go round to our orders, payments and
tickets, projects and add in that test colon C.I. script to each them.
So back inside, my editor.
Or excuse me, first inside of our terminal.
Let's make sure that we're making these changes to the master branch.
I'm going to change back over to a master first.
Then I'll go back over.
Technically, that didn't matter, we could have just made the changes, why we're on the dev branch
and then check out M..
But whatever.
I just want to make the point that we want to make these changes to the master branch.
So we're going to go around to our orders, payments and ticket services and add in that new test command.
So first off, inside of Porter's of on the packages on file, we'll add in test S.I.
There's one, I'll save the file and it.
Next up is payments.
Don't put in test, see, I just save it.
And then last one, our ticket service.
Just and save it.
All right, so let's save that.
Well, then go back over to our terminal.
We're going to commit these three change packages on files and then push them up.
We'll do a get add.
I need to make sure I add everything from my route project directory, I cannot add from directly inside
of off.
We'll do a get ad from ticketing now if I do get status.
I should see those three files added.
All commit those changes with the message of added test script.
And then before we try to push these changes, we did just make a change to our master branch.
So we have to pull those changes down first.
I'll do a get pull origin, master.
That's going to merge in those changes once again, you're going to be prompted with an editor.
You can just close the editor out.
Gay marriage.
Those changes in.
And now I can push these up, so get push or Ajin Master.
All right.
Just make sure that we are totally on the same page at this point in time.
We should be able to go back over to get hub, refresh our repository, see all four workflow files
inside the master branch in the DOD, get hub slash workflows file folder.
I should be able to also go back or to my main ticketing directory, go in to, say, the payments service.
Take a look at the packages on file and see the test see script inside there.
And you should build to see that TCI script inside of the orders, payments, tickets, services package
based on files.
All right.
So we've taking a long time here.
So let's now take a pause.
We're going to come back.
Next video, make one more change to our dev branch.
Push it up and then make sure that we run all the tests over our entire project in parallel.
So we'll take you to that in just a moment.