1
00:00:00,420 --> 00:00:06,990
All right, so now our code has been checked in in the GitHub repo, and now I'm going to start working

2
00:00:06,990 --> 00:00:10,040
with the GitHub action, so I'm going to click this action step.

3
00:00:10,050 --> 00:00:16,920
So if you have GitHub actions enabled or already available for your Reppel, you should see this action

4
00:00:16,920 --> 00:00:21,660
stab for Europos, which is the reason why I'm actually seeing this guy.

5
00:00:21,960 --> 00:00:27,420
And then I need to start creating a workflow over here and I'm going to see how it actually works.

6
00:00:27,450 --> 00:00:32,870
So once you do this GitHub actions, once you create this, it is automatically going to suggest you

7
00:00:32,880 --> 00:00:35,140
the type of repo you're going to be working with.

8
00:00:35,310 --> 00:00:38,730
It's telling that the workflows made up your typescript repository that you have.

9
00:00:38,730 --> 00:00:46,410
But what originally this project is not only just typescript, it is also a mixture of both JavaScript

10
00:00:46,410 --> 00:00:47,360
and TypeScript.

11
00:00:47,580 --> 00:00:52,640
So probably we need to have like a Norges project, things of that nature.

12
00:00:52,830 --> 00:00:57,780
So I'm just going to select this, set up a workflow yourself option over here.

13
00:00:58,140 --> 00:01:05,850
And then you can see that it is going to bring us a lot of options, something like a controls and then

14
00:01:05,850 --> 00:01:10,150
on and then workflow and then the jobs and things of that nature.

15
00:01:10,170 --> 00:01:15,300
So it's going to run on the Ubuntu latest and the script is going to be these and then things of that

16
00:01:15,300 --> 00:01:15,640
nature.

17
00:01:15,660 --> 00:01:22,170
I mean, this is like a default pre popular template of data that is going to be showing over here.

18
00:01:22,500 --> 00:01:25,470
But you can also change the steps if you want.

19
00:01:25,470 --> 00:01:32,340
Like, you can just add a set up Norges environment and you can see that it's going to bring up all

20
00:01:32,340 --> 00:01:34,780
the set up environment information.

21
00:01:34,970 --> 00:01:39,740
Well, as I said, I'm actually going to start creating my own jobs over here.

22
00:01:39,750 --> 00:01:45,270
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

23
00:01:45,270 --> 00:01:45,630
good.

24
00:01:45,630 --> 00:01:49,620
And I don't really need to allow this workflow or dispatch.

25
00:01:49,620 --> 00:01:53,160
I don't require this guy, but I need to create a jobs.

26
00:01:53,370 --> 00:02:02,430
And you can also create a strategy like The Matrix to run on a on different versions of the NORGAY'S

27
00:02:02,430 --> 00:02:03,380
if you really want to.

28
00:02:03,390 --> 00:02:06,210
I mean, you can do that as well.

29
00:02:06,210 --> 00:02:11,280
If you really want to strategy, you see that it brings you up the strategy up.

30
00:02:11,490 --> 00:02:14,130
And if I had the center then it's going to show you the Matrix.

31
00:02:14,430 --> 00:02:20,190
And then if you set the keys, it is going to show you the node hyphen version.

32
00:02:20,190 --> 00:02:26,970
You can just type the hyphen version where you can set the versions, something like 10 sticks and two

33
00:02:27,010 --> 00:02:32,070
old X and the latest version, probably like 14. X, something like that.

34
00:02:32,430 --> 00:02:37,530
So you can run the test on three different versions of naughties if you want to.

35
00:02:37,740 --> 00:02:43,410
But you don't really have to add this if you think your code is going to run automatically in the explosion

36
00:02:43,410 --> 00:02:43,870
itself.

37
00:02:43,890 --> 00:02:47,040
I mean, this is one other way that you can do it or here.

38
00:02:47,040 --> 00:02:51,180
I mean, just like additional information that I'm actually adding it over here.

39
00:02:51,630 --> 00:02:58,500
And once this is done, I actually need to go with our Blairites GitHub action option, which has been

40
00:02:58,500 --> 00:02:59,730
specified this guy.

41
00:03:00,030 --> 00:03:00,360
Right.

42
00:03:00,610 --> 00:03:04,890
So I'm just going to use the same step over here to copy this.

43
00:03:05,310 --> 00:03:12,990
And I'm going to just remove these old guys, pays these guys over here very, very simple, straightforward.

44
00:03:12,990 --> 00:03:17,760
Let's go check out the code and set up the node and then it's going to set up the playwright actions,

45
00:03:18,570 --> 00:03:22,290
GitHub actions, and then it's going to install the dependencies and then it's going to run the test

46
00:03:22,440 --> 00:03:24,480
and you'll see that that is an option.

47
00:03:24,480 --> 00:03:28,020
Again, pm est I mean to run the NPM test, right.

48
00:03:28,290 --> 00:03:29,500
We know what we are going to be doing.

49
00:03:29,640 --> 00:03:34,950
We already have the command to be executed for running our tests.

50
00:03:34,960 --> 00:03:37,000
That's what we will be doing.

51
00:03:37,350 --> 00:03:44,040
So the command is nothing but the NPCs Foleo half of Perram browser name as chromium.

52
00:03:44,430 --> 00:03:51,180
Uh that's if not the headful don't do the headful because you need to install the X VFP and stuff to

53
00:03:51,180 --> 00:03:54,150
run on a machine which has a display device connected.

54
00:03:54,360 --> 00:03:55,290
So I'm, I'm going to do that.

55
00:03:55,650 --> 00:04:02,940
I'm not checking this code with this parameter and then I'm going to start to commit, uh, that first

56
00:04:04,350 --> 00:04:05,100
workflow.

57
00:04:05,730 --> 00:04:07,560
I'm going to commit the new file.

58
00:04:08,250 --> 00:04:08,850
That's it.

59
00:04:09,360 --> 00:04:11,270
So you can see that this is very, very simple.

60
00:04:11,280 --> 00:04:14,430
Now, we have created the first workflow with the GitHub action.

61
00:04:14,440 --> 00:04:20,370
So now if I go to the actions, you can see that the action is currently under execution.

62
00:04:20,550 --> 00:04:27,540
And if I click D.C.I, you can see that the, uh, the action is going to be running on the Matrix job.

63
00:04:27,900 --> 00:04:33,420
So this matrix build is actually going to run on three different versions, like 10 or 12 and 14, not

64
00:04:33,420 --> 00:04:33,750
X.

65
00:04:34,350 --> 00:04:35,490
That's what I was talking about.

66
00:04:35,490 --> 00:04:42,270
Like, you have the power to run that test on different versions of Norges and now let's choose any

67
00:04:42,270 --> 00:04:49,710
one of the version that, say, 12. X, and you can see that it's running the right GitHub actions.

68
00:04:51,120 --> 00:04:54,990
So it's downloading all the dependencies for us, just quite good.

69
00:05:00,620 --> 00:05:08,120
And you can see that it is running or npm install and then be a Foleo Perram browser name of chromium,

70
00:05:08,570 --> 00:05:14,810
and now that's the reason I was talking about in my first video of the section that we need to run this

71
00:05:14,810 --> 00:05:16,010
test using one command.

72
00:05:16,340 --> 00:05:24,680
And because all our test, which is written in other sections, are in a Amarasinghe method, we cannot

73
00:05:24,680 --> 00:05:27,290
really run the test just like a one command order.

74
00:05:27,290 --> 00:05:31,820
And that's the reason I need to have some sort of test execution command, which is nothing but a test

75
00:05:31,830 --> 00:05:33,470
run which can do things for us.

76
00:05:33,710 --> 00:05:39,290
And you can see that with this command, like NPCs Foleo, we they will run all our test and all our

77
00:05:39,290 --> 00:05:40,820
tests has got past as well.

78
00:05:40,820 --> 00:05:45,740
Like seven second, they all completed executing the test and the giddap action is successfully running

79
00:05:45,740 --> 00:05:47,800
as well, which is quite good and interesting.

80
00:05:48,140 --> 00:05:55,460
This is why we wanted to run the test using test runner and GitHub actions and playwright test with

81
00:05:55,460 --> 00:05:58,590
giddap actions is super easy and super awesome as well.

82
00:05:58,850 --> 00:06:03,580
Now you can see that the test is actually running fine on the GitHub actions, which is quite good.

83
00:06:03,830 --> 00:06:08,930
We have already made it and additional information regarding uploading the artifacts.

84
00:06:08,930 --> 00:06:10,550
We are going to do that as well.

85
00:06:10,580 --> 00:06:15,080
So in order to work with the artifacts in first place, I want to show you what we are going to be doing

86
00:06:15,080 --> 00:06:15,530
basically.

87
00:06:15,930 --> 00:06:22,370
So instead of the headful alone, if we just specify the video, let's assume so.

88
00:06:22,370 --> 00:06:28,070
If I just run the test on the different browsers, if I want to generate the video, if I just specify

89
00:06:28,070 --> 00:06:33,530
video options of our playwrite test run, or if you remember what I was showing you, the different

90
00:06:33,680 --> 00:06:39,440
Perram options, there is also a video option which is going to record a video for you, and then it's

91
00:06:39,440 --> 00:06:46,490
going to put all the result on a test hyphen results folder for us, which is quite good and interesting.

92
00:06:46,790 --> 00:06:50,030
And that's exactly what we'll be doing in this place.

93
00:06:50,270 --> 00:06:50,410
Well.

94
00:06:50,990 --> 00:06:53,450
I'm just going to be running all the tests on the video.

95
00:06:53,690 --> 00:06:59,060
It seems like with the video there is some issue going on, but that's all right.

96
00:06:59,330 --> 00:07:02,600
And now if I just go here, let me refresh.

97
00:07:03,680 --> 00:07:06,380
Do we have a folder, car video?

98
00:07:06,590 --> 00:07:07,790
Oh, it's on the play.

99
00:07:07,880 --> 00:07:08,930
I see I said so.

100
00:07:09,060 --> 00:07:10,070
That's true, unless.

101
00:07:11,610 --> 00:07:18,270
So we have a test results folder, so if I just go to the test, I found the results.

102
00:07:19,800 --> 00:07:21,030
And Alice.

103
00:07:22,230 --> 00:07:29,560
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!

104
00:07:32,610 --> 00:07:39,720
Oh, we have a lot of folder there, so you can see that we have a webcam file, just nothing but the

105
00:07:39,960 --> 00:07:45,630
video file, which is going to be executed while it's going to run the test for us, which is quite

106
00:07:45,630 --> 00:07:45,920
good.

107
00:07:45,930 --> 00:07:50,500
I mean, it is going to be working fine with the video creation as well.

108
00:07:50,940 --> 00:07:53,730
So let me just open the folder.

109
00:07:53,910 --> 00:08:01,350
And if I just see this year video the creation of the Web and file, probably.

110
00:08:05,520 --> 00:08:12,600
Nothing has really happened there, none of the video is being captured there, so let me try running

111
00:08:12,600 --> 00:08:13,460
them again.

112
00:08:13,930 --> 00:08:17,210
Seems like the end to end user creation is always failing.

113
00:08:17,220 --> 00:08:20,610
So let's quickly see what's going on with the ID aspect.

114
00:08:20,610 --> 00:08:30,690
Artists file this guy, and if we just go all the way here, I don't see there is any issues with that

115
00:08:30,690 --> 00:08:31,590
particular option.

116
00:08:31,590 --> 00:08:36,630
So maybe I'm just going to remove this, wait until and I'm going to save this guy.

117
00:08:37,770 --> 00:08:39,780
And I want to run this guy in.

118
00:08:42,670 --> 00:08:49,480
And this is happening just while we do the video, so if I just roll and head full of video, probably

119
00:08:50,770 --> 00:08:52,090
we'll see what is the behavior.

120
00:08:53,570 --> 00:08:56,480
So the extra automation side is actually working fine.

121
00:08:58,100 --> 00:08:59,590
I would do that in the headful mode.

122
00:09:02,560 --> 00:09:09,370
And it's quite interesting to see that always just this message is coming up like it starts.

123
00:09:09,850 --> 00:09:16,630
This is actually failing over here while the test is actually executing fine while we see them in the

124
00:09:16,630 --> 00:09:18,430
headless headful mode as well.

125
00:09:18,730 --> 00:09:19,930
This is quite interesting.

126
00:09:19,960 --> 00:09:22,030
So if I just remove this video option.

127
00:09:24,430 --> 00:09:29,950
And the test has not passed, which is quite crazy to me, because this shouldn't behave in this fashion

128
00:09:29,950 --> 00:09:30,550
definitely.

129
00:09:30,850 --> 00:09:38,770
And I think this is kind of a bug with the Foleo because still the Foleo is in the beta stage and they

130
00:09:38,770 --> 00:09:39,930
are not released yet.

131
00:09:40,180 --> 00:09:42,430
So I think there is something crazy going on.

132
00:09:43,150 --> 00:09:46,360
Maybe this bug is going to be fixed pretty soon, which I'm not sure.

133
00:09:46,360 --> 00:09:49,810
But definitely this is going to be looking it's looking pretty much like a bug to me.

134
00:09:50,400 --> 00:09:57,010
Oh, well, we'll see if this guy is going to work with our GitHub actions over here and we'll see how

135
00:09:57,010 --> 00:09:57,790
it actually works.

136
00:09:57,790 --> 00:10:02,350
If I specify with you, I mean, you can do it yourself if you want, because by now all you can do

137
00:10:02,350 --> 00:10:03,730
is change the workflow.

138
00:10:04,060 --> 00:10:05,820
If not, I'm going to do that in the next video.