1
00:00:00,680 --> 00:00:06,440
Welcome to next section of our course into Test Automation with playwright, and in this section, we

2
00:00:06,440 --> 00:00:12,140
are going to talk about all the different integrations that we can make with playwright and how we can

3
00:00:12,140 --> 00:00:19,550
extend executing the playwright in different kayaked platforms so playwright can be extended to be executed

4
00:00:19,550 --> 00:00:26,690
in multiple different platforms like Adjure develops, GitHub actions, docker container images, or

5
00:00:26,690 --> 00:00:32,870
you can even run in Jenkins or Circusy and mini series or whatever is that you can name it because the

6
00:00:32,870 --> 00:00:39,830
execution of the test in playwrite is very, very simple, because we all know that playwrite, if we

7
00:00:39,830 --> 00:00:46,640
talk about the JavaScript binding or the types binding, it is just a JavaScript file and in the Java

8
00:00:46,640 --> 00:00:50,810
file it is even more simpler because it is just an MAVEN dependency that you're going to be adding and

9
00:00:50,810 --> 00:00:51,170
executing.

10
00:00:51,170 --> 00:00:56,240
The test is going to be pretty much exactly the same, like how you run the test in other testing tools

11
00:00:56,240 --> 00:00:59,480
like selenium or protractor or something like that.

12
00:00:59,660 --> 00:01:04,760
And similarly, if you take the C sharp language binding, the integration is going to be once again

13
00:01:04,760 --> 00:01:09,440
similar because all it's going to do is going to be restoring the Newgate package and then run the test

14
00:01:09,440 --> 00:01:09,790
for you.

15
00:01:10,010 --> 00:01:12,380
So those things remain still the same.

16
00:01:12,380 --> 00:01:14,620
There is no change on different language bindings.

17
00:01:14,630 --> 00:01:16,220
It's going to be pretty much exactly the same.

18
00:01:16,430 --> 00:01:20,780
But in this integration that we're going to be talking about, we are going to be focusing on playwrite

19
00:01:20,780 --> 00:01:28,130
integration to be running on GitHub actions as you ops and docker container images and all those things

20
00:01:28,130 --> 00:01:30,740
in JavaScript and typescript language binding.

21
00:01:30,770 --> 00:01:33,880
That's what we'll be discussing in this integration section.

22
00:01:34,190 --> 00:01:39,200
So this is going to be very, very common scenario where you will be using playwrite to integrate running

23
00:01:39,200 --> 00:01:41,180
in these different platforms.

24
00:01:41,180 --> 00:01:42,350
And that's what we'll be discussing.

25
00:01:42,530 --> 00:01:48,260
And the first lecture of this section is going to be integrating GitHub actions and followable.

26
00:01:48,260 --> 00:01:54,380
That will be talking about how we can integrate playwrite to be running on the azure develops and forward.

27
00:01:54,400 --> 00:01:59,170
That will be seeing how we can run the playwright in the docker containers and stuff.

28
00:01:59,360 --> 00:02:02,540
That's how this section is going to be looking like.

29
00:02:03,020 --> 00:02:07,840
So starting our next video, we're discussing all those integration and we'll see how it actually works.