WEBVTT 00:00.640 --> 00:07.770 In our last video we created and custom agent in our own custom pool of agents. 00:07.780 --> 00:15.220 And we also saw how we can execute the bird using this particular agent or this particular Udemy pool 00:15.250 --> 00:16.690 that we just created. 00:16.690 --> 00:18.100 So it was always working fine. 00:18.100 --> 00:24.760 And we also saw how we can get the published output or there and everything was working as expected 00:24.970 --> 00:26.610 which was pretty cool. 00:26.710 --> 00:34.960 And now that I want to see how we can publish a zip artifact of the darknet core the publication that 00:34.960 --> 00:42.400 I have so I can also write a task something like this which is gonna be publishing my application in 00:42.400 --> 00:49.540 a zip file something like this as an artifact and then I can use this for deploying into my ISIS server 00:49.540 --> 00:51.100 in my local machine. 00:51.100 --> 00:56.650 So these are something that we can do while doing the execution of our bird and also we can see how 00:56.650 --> 00:57.460 things work. 00:57.460 --> 01:05.380 So basically while we do the bird we don't really try to execute or even reply the application within 01:05.380 --> 01:12.490 our Internet Information Server or ISIS is rather we do their deployment actually in the release cycle 01:12.580 --> 01:14.270 which is in the released pipeline. 01:14.290 --> 01:21.130 We don't do that in the bird pipeline but in reality you actually need to have the artifacts which is 01:21.130 --> 01:25.700 something that you need to be deployed during the release cycle. 01:26.080 --> 01:32.770 So now I'm saying a new terminology called artifacts which is something that you obtain in the process 01:32.770 --> 01:43.690 of build process and then you deploy that particular artifact in the release cycle in one of the machines. 01:43.690 --> 01:49.050 So basically in some companies they only use the bid process for the release process. 01:49.060 --> 01:54.900 They actually use a third party tool something like team city or octopus. 01:55.060 --> 02:01.150 And some of the most popular tools which are available in the market which actually do the deployment 02:01.270 --> 02:03.660 of the application in their own machine. 02:03.760 --> 02:09.520 And I have seen many companies doing their own practices and the most popular these days are octopus 02:09.760 --> 02:15.610 which actually do the deployment of the application in a remote machine or maybe in a remote virtual 02:15.610 --> 02:16.920 machine or something like that. 02:17.080 --> 02:23.830 But you can do the exact same thing using the release of the as your pipelines which does that thing 02:24.100 --> 02:30.490 but I'm actually not going to talk about the release yet but I'm going to show you how the actual pipeline 02:30.520 --> 02:37.540 is going to work and how things are actually working so you can see that the build has been maybe completed. 02:37.540 --> 02:41.320 So if I do a refresh here. 02:41.320 --> 02:41.800 Right. 02:42.040 --> 02:42.880 It's still loading 02:46.110 --> 02:47.410 I mean go inside. 02:47.510 --> 02:56.750 You can see that it is trying to do the initialize doing the checkout then it's copying the file into 02:56.750 --> 03:00.860 our machine and then now it is trying to publish the bird artifacts. 03:00.890 --> 03:07.640 You can see that this is the one which of us talking about it is gonna zip that particular file and 03:07.640 --> 03:11.010 then you can see here the final stuff has been done. 03:11.450 --> 03:17.570 Now if I go to the summary you can see that there is this drop file and if I go to the view content 03:17.610 --> 03:18.330 this time. 03:18.410 --> 03:18.610 Yeah. 03:18.620 --> 03:25.600 Earlier we saw just the selenium test card but this time you'll also see a year demo app dart zip. 03:25.610 --> 03:32.330 So this is the application zip file which actually has our application and the UI test actually holds 03:32.330 --> 03:37.280 are the selenium rated stuff which is gonna be used for executing our test. 03:37.280 --> 03:43.370 So this is how we can actually do the things off deployment in the boot process began. 03:43.370 --> 03:49.630 Also do one more cheat here we can create selenium test to run and see how it actually works. 03:49.640 --> 03:54.740 We can extend the same thing for our release cycle as well. 03:54.950 --> 04:01.580 So what I'm going to do is I'm going to do an edit here and then after this particular zip past been 04:01.580 --> 04:08.150 done I would like to see if I could able to run a selenium test so I can go to the task and I can search 04:08.150 --> 04:12.200 for test and you can see that is something called us versus studio test. 04:12.320 --> 04:24.680 I'm gonna select that and I know that my test has a deal of the stars char grips so I'm just going to 04:24.680 --> 04:33.200 copy this guy I'm going to paste it and I'm I know I know that I have something called s selenium or 04:33.200 --> 04:42.140 here and I'm just gonna do this guy as it is and it contains a mix of you test so you need to check 04:42.140 --> 04:46.940 this because we'll need then it'll make the test session running an interactive mode so I'm going to 04:46.940 --> 04:52.190 do that I'm going to leave the test platform as latest because I actually have some sort of 20 19 installed 04:52.190 --> 04:58.720 in my machine so I'm just going to do that and I'm going to set everything as it is for now I'm not 04:58.730 --> 05:04.940 going to run things in parallel as of now and I'm gonna just add that and you can see that it has added 05:04.940 --> 05:07.250 things for me or here. 05:07.910 --> 05:13.790 So I'm basically going to run this and maybe I don't do required this particular search folder because 05:13.790 --> 05:21.190 sometimes it won't work expected so I'm just gonna remove that and I'm going to hit safe right. 05:21.250 --> 05:23.290 And then I see this again. 05:23.300 --> 05:29.780 And now if I tried to run this what would happen is it is going to burn at the exact same thing which 05:29.780 --> 05:31.230 was happening before. 05:31.280 --> 05:37.970 So it's going to run the run the build process then it is going to reply the it's gonna create a zip 05:37.970 --> 05:45.950 file and also it is going to run these selenium tests that we have in our repo and then it's going to 05:45.950 --> 05:48.180 run that for me in my local machine. 05:48.200 --> 05:49.370 Of course it is going to fail. 05:49.370 --> 05:54.680 As of now the reason is because it has not deployed in my internal information so yet. 05:54.680 --> 05:56.200 So that's why the test is gonna fail. 05:56.330 --> 06:01.070 But you can still see the flavour of the test running in my local machine. 06:01.070 --> 06:02.780 So we'll see what's really happening. 06:03.320 --> 06:05.690 So let's go to the bullet came 06:10.660 --> 06:17.560 and you can see that the execution is happening right now it has dared to publish and then the V.S. 06:17.560 --> 06:18.010 test. 06:18.030 --> 06:24.330 I was expecting the test to happen but I don't think it has really happened here. 06:24.540 --> 06:32.790 So let me see what has happened and it says that it wouldn't be able to find the matching assemblies 06:32.880 --> 06:36.030 which is nothing but the selenium data. 06:36.480 --> 06:40.320 So I'm just going to go back to the bird again. 06:40.320 --> 06:42.020 I know what is the problem basically. 06:42.390 --> 06:44.240 So if I do that I did. 06:44.250 --> 06:50.000 So here you can see that this particular slash is making the difference basically. 06:50.100 --> 06:57.040 So we need to have this particular input to be a little more dynamic. 06:57.060 --> 07:00.260 So this is not the way I should be looking like. 07:00.360 --> 07:06.630 So I'm basically going to be doing exactly the same thing but in a different sense. 07:06.630 --> 07:12.070 I'm just gonna have the input like test Assembly version to set any of us first and then testing out 07:12.300 --> 07:18.130 and test adapter and object and then I'm just gonna hit safe. 07:18.360 --> 07:26.580 I will also add the search folder which is something required and then I'm gonna hit run. 07:26.640 --> 07:31.010 So this way it is going to be running the whole things for us. 07:31.140 --> 07:32.040 See what's going to happen. 07:33.140 --> 07:36.820 Now you can see that it is currently running the dominant bird release. 07:36.870 --> 07:43.450 And I would expect this time something sure to happen for the obvious test. 07:43.660 --> 07:44.240 There you go. 07:44.580 --> 07:48.450 You can see that it is actually running the selenium test for me. 07:48.450 --> 07:51.710 It has opened the browser but it has closed that. 07:51.810 --> 07:56.720 And the reason is fine because we have been trying to run the whole test here. 07:56.730 --> 08:01.530 We're just trying to see if that particular Chrome browser is at least card and it has opened or not 08:01.770 --> 08:03.570 I could see that that's actually happening. 08:03.570 --> 08:12.090 So now if I go to the bird and I go to the summary you can see that it actually shows that the test 08:12.090 --> 08:13.120 has got failed. 08:13.160 --> 08:19.760 So there is a nice report here saying there is a total one test and it has got failed and it has like 08:19.770 --> 08:22.620 zero percent of passing rate just fine. 08:22.920 --> 08:30.630 And also shows that doing the execution there was something wrong and it was not handled. 08:30.630 --> 08:31.720 So there is a window. 08:31.740 --> 08:39.450 Ed reporting do not show you a not set window enter dialog pops up in the middle that the UI test execution 08:39.480 --> 08:41.910 then the test will hang. 08:41.910 --> 08:43.010 So right. 08:43.020 --> 08:50.310 So this kind of warning and now if I just go back to the boat over here and if I go to the test you 08:50.310 --> 08:55.530 can see that the same report comes in for us like what's really happening behind the scene. 08:55.530 --> 09:01.350 And once I click that test it also shows me that there is no such element to locate which is fine because 09:01.350 --> 09:04.970 as I said before our application has not been deployed yet. 09:05.160 --> 09:11.430 And that's the reason the test is currently failing and we could able to see that this is going to be 09:11.430 --> 09:17.220 throwing us an error which is fine for now because in our release cycle or in the released pipeline 09:17.490 --> 09:19.760 we will see that this whole test will actually pass. 09:19.770 --> 09:22.430 It won't be complaining as these kinds of matter. 09:22.550 --> 09:29.640 So that's it guys is how we can actually add the build a pipeline to have the selenium test as well 09:29.970 --> 09:36.720 you know the next video will do exactly the same thing but I'm going to show you the taste of the classical 09:36.840 --> 09:41.130 pipeline instead of using the modern Jamel pipeline.