All right, so now our code has been checked in in the GitHub repo, and now I'm going to start working
with the GitHub action, so I'm going to click this action step.
So if you have GitHub actions enabled or already available for your Reppel, you should see this action
stab for Europos, which is the reason why I'm actually seeing this guy.
And then I need to start creating a workflow over here and I'm going to see how it actually works.
So once you do this GitHub actions, once you create this, it is automatically going to suggest you
the type of repo you're going to be working with.
It's telling that the workflows made up your typescript repository that you have.
But what originally this project is not only just typescript, it is also a mixture of both JavaScript
and TypeScript.
So probably we need to have like a Norges project, things of that nature.
So I'm just going to select this, set up a workflow yourself option over here.
And then you can see that it is going to bring us a lot of options, something like a controls and then
on and then workflow and then the jobs and things of that nature.
So it's going to run on the Ubuntu latest and the script is going to be these and then things of that
nature.
I mean, this is like a default pre popular template of data that is going to be showing over here.
But you can also change the steps if you want.
Like, you can just add a set up Norges environment and you can see that it's going to bring up all
the set up environment information.
Well, as I said, I'm actually going to start creating my own jobs over here.
So what I'm going to do is I'm just going to leave these guys like name FCI on as this, which is all
good.
And I don't really need to allow this workflow or dispatch.
I don't require this guy, but I need to create a jobs.
And you can also create a strategy like The Matrix to run on a on different versions of the NORGAY'S
if you really want to.
I mean, you can do that as well.
If you really want to strategy, you see that it brings you up the strategy up.
And if I had the center then it's going to show you the Matrix.
And then if you set the keys, it is going to show you the node hyphen version.
You can just type the hyphen version where you can set the versions, something like 10 sticks and two
old X and the latest version, probably like 14. X, something like that.
So you can run the test on three different versions of naughties if you want to.
But you don't really have to add this if you think your code is going to run automatically in the explosion
itself.
I mean, this is one other way that you can do it or here.
I mean, just like additional information that I'm actually adding it over here.
And once this is done, I actually need to go with our Blairites GitHub action option, which has been
specified this guy.
Right.
So I'm just going to use the same step over here to copy this.
And I'm going to just remove these old guys, pays these guys over here very, very simple, straightforward.
Let's go check out the code and set up the node and then it's going to set up the playwright actions,
GitHub actions, and then it's going to install the dependencies and then it's going to run the test
and you'll see that that is an option.
Again, pm est I mean to run the NPM test, right.
We know what we are going to be doing.
We already have the command to be executed for running our tests.
That's what we will be doing.
So the command is nothing but the NPCs Foleo half of Perram browser name as chromium.
Uh that's if not the headful don't do the headful because you need to install the X VFP and stuff to
run on a machine which has a display device connected.
So I'm, I'm going to do that.
I'm not checking this code with this parameter and then I'm going to start to commit, uh, that first
workflow.
I'm going to commit the new file.
That's it.
So you can see that this is very, very simple.
Now, we have created the first workflow with the GitHub action.
So now if I go to the actions, you can see that the action is currently under execution.
And if I click D.C.I, you can see that the, uh, the action is going to be running on the Matrix job.
So this matrix build is actually going to run on three different versions, like 10 or 12 and 14, not
X.
That's what I was talking about.
Like, you have the power to run that test on different versions of Norges and now let's choose any
one of the version that, say, 12. X, and you can see that it's running the right GitHub actions.
So it's downloading all the dependencies for us, just quite good.
And you can see that it is running or npm install and then be a Foleo Perram browser name of chromium,
and now that's the reason I was talking about in my first video of the section that we need to run this
test using one command.
And because all our test, which is written in other sections, are in a Amarasinghe method, we cannot
really run the test just like a one command order.
And that's the reason I need to have some sort of test execution command, which is nothing but a test
run which can do things for us.
And you can see that with this command, like NPCs Foleo, we they will run all our test and all our
tests has got past as well.
Like seven second, they all completed executing the test and the giddap action is successfully running
as well, which is quite good and interesting.
This is why we wanted to run the test using test runner and GitHub actions and playwright test with
giddap actions is super easy and super awesome as well.
Now you can see that the test is actually running fine on the GitHub actions, which is quite good.
We have already made it and additional information regarding uploading the artifacts.
We are going to do that as well.
So in order to work with the artifacts in first place, I want to show you what we are going to be doing
basically.
So instead of the headful alone, if we just specify the video, let's assume so.
If I just run the test on the different browsers, if I want to generate the video, if I just specify
video options of our playwrite test run, or if you remember what I was showing you, the different
Perram options, there is also a video option which is going to record a video for you, and then it's
going to put all the result on a test hyphen results folder for us, which is quite good and interesting.
And that's exactly what we'll be doing in this place.
Well.
I'm just going to be running all the tests on the video.
It seems like with the video there is some issue going on, but that's all right.
And now if I just go here, let me refresh.
Do we have a folder, car video?
Oh, it's on the play.
I see I said so.
That's true, unless.
So we have a test results folder, so if I just go to the test, I found the results.
And Alice.
And you can see that we have a test as well, so if I just call it your test and analysis and E to E!
Oh, we have a lot of folder there, so you can see that we have a webcam file, just nothing but the
video file, which is going to be executed while it's going to run the test for us, which is quite
good.
I mean, it is going to be working fine with the video creation as well.
So let me just open the folder.
And if I just see this year video the creation of the Web and file, probably.
Nothing has really happened there, none of the video is being captured there, so let me try running
them again.
Seems like the end to end user creation is always failing.
So let's quickly see what's going on with the ID aspect.
Artists file this guy, and if we just go all the way here, I don't see there is any issues with that
particular option.
So maybe I'm just going to remove this, wait until and I'm going to save this guy.
And I want to run this guy in.
And this is happening just while we do the video, so if I just roll and head full of video, probably
we'll see what is the behavior.
So the extra automation side is actually working fine.
I would do that in the headful mode.
And it's quite interesting to see that always just this message is coming up like it starts.
This is actually failing over here while the test is actually executing fine while we see them in the
headless headful mode as well.
This is quite interesting.
So if I just remove this video option.
And the test has not passed, which is quite crazy to me, because this shouldn't behave in this fashion
definitely.
And I think this is kind of a bug with the Foleo because still the Foleo is in the beta stage and they
are not released yet.
So I think there is something crazy going on.
Maybe this bug is going to be fixed pretty soon, which I'm not sure.
But definitely this is going to be looking it's looking pretty much like a bug to me.
Oh, well, we'll see if this guy is going to work with our GitHub actions over here and we'll see how
it actually works.
If I specify with you, I mean, you can do it yourself if you want, because by now all you can do
is change the workflow.
If not, I'm going to do that in the next video.