All right, so with some bugs, with our Foleo, while we are trying to execute the video option, I'm
definitely sure this is going to happen even if I tried to run over here.
But I'm just going to keep my fingers crossed and I'm going to be trying to execute the same test over
here on my GitHub actions as well.
And I will try to see if this code is going to work.
So what I'm going to do is I'm going to go to the GitHub actions.
I'm going to go view the workflow file.
And what I'm going to do is like I'm going to add the additional upload artifact option, which is specified
on the end of the step in the playwright aspect.
So I'm just going to go over here.
I'm going to use this useless option, which is going to be taking a creating an artifact and then it's
going to put from the path test results and then is going to create the artifact as zip file for us
once the testing situation is fully completed.
So this is what is this particular command which is specified on the play right over here?
This is exactly what I am trying to do instead of bacteriophage to have changes to test results.
So I'm going to come out and say Outhred artifacts option.
And before doing even that, I also need to add the severo, right?
I mean, only if I create a video is going to create an artifact for us.
If not, that's not going to work.
So I just consider that.
So it's going to create a video and then it is going to upload the videos for us on the artifact.
That is the whole idea of having an artifact.
I'm definitely not sure if that video is going to work for us or not because we saw that for some reason
it was not working.
The video wasn't not even playing because we have some failures.
We're just trying to execute, but fingers crossed and trying to run that test and we'll see what's
going to basically happen.
There you go.
Fortunately, there are four tests got passed this time and to discard Skip and one does not fail,
which just this one, I think, on our normal execution on our machine was three days passed to the
captain, to the Scott failed.
At least that is an improvement on the Kitab action side.
And you can see that it is actually passing on version 14 of Norges, but not on 10 and 12.
This is the reason I actually added to The Matrix that it actually works for a specific version, but
not for the other other versions.
So you can see that in version number 14, all the discard passed and the other two discard failed on
the 12 and 10, which is quite good to see that actually on this version.
This is the artifact loading is passing verus on emotional intelligence, not even my machine.
I think I have the older version and that's why it got failed.
And the pass to the new version is actually working fine, which is a good news for us as well.
I mean, I just know that.
And now if I go back to my GitHub actions over here, this guy, uh, got past.
So you can see that two of them got failed.
One of them got passed.
And there is a test artifact as well.
So if I just open this artifact, you can see that the artifact has been downloaded for us.
Just open this guy and there is the IR test, chromium Dynex, and we have three of them file.
So if I just open this file, you can see that it has e actually executed the test and it is working
fine as well, which is quite good.
And if I just open the other one, this is there should be different version, I guess.
So it's working fine.
And similarly, if I just go to the test run or test.
You can see that it has now added to the neo indited website as well, which is quite good.
So it is working fine, version 14 of the node, and it's not working for version 10 and 12, which
is quite good.
And we could able to see that is working fine while we do the matrix option.
So that's it, guys.
This is how we can actually work with GitHub actions on integrating GitHub actions and integrating playwrite
with GitHub actions.
Mido next lecture by integrating playwrite with the WAPs.