In our last video we created and custom agent in our own custom pool of agents.
And we also saw how we can execute the bird using this particular agent or this particular Udemy pool
that we just created.
So it was always working fine.
And we also saw how we can get the published output or there and everything was working as expected
which was pretty cool.
And now that I want to see how we can publish a zip artifact of the darknet core the publication that
I have so I can also write a task something like this which is gonna be publishing my application in
a zip file something like this as an artifact and then I can use this for deploying into my ISIS server
in my local machine.
So these are something that we can do while doing the execution of our bird and also we can see how
things work.
So basically while we do the bird we don't really try to execute or even reply the application within
our Internet Information Server or ISIS is rather we do their deployment actually in the release cycle
which is in the released pipeline.
We don't do that in the bird pipeline but in reality you actually need to have the artifacts which is
something that you need to be deployed during the release cycle.
So now I'm saying a new terminology called artifacts which is something that you obtain in the process
of build process and then you deploy that particular artifact in the release cycle in one of the machines.
So basically in some companies they only use the bid process for the release process.
They actually use a third party tool something like team city or octopus.
And some of the most popular tools which are available in the market which actually do the deployment
of the application in their own machine.
And I have seen many companies doing their own practices and the most popular these days are octopus
which actually do the deployment of the application in a remote machine or maybe in a remote virtual
machine or something like that.
But you can do the exact same thing using the release of the as your pipelines which does that thing
but I'm actually not going to talk about the release yet but I'm going to show you how the actual pipeline
is going to work and how things are actually working so you can see that the build has been maybe completed.
So if I do a refresh here.
Right.
It's still loading
I mean go inside.
You can see that it is trying to do the initialize doing the checkout then it's copying the file into
our machine and then now it is trying to publish the bird artifacts.
You can see that this is the one which of us talking about it is gonna zip that particular file and
then you can see here the final stuff has been done.
Now if I go to the summary you can see that there is this drop file and if I go to the view content
this time.
Yeah.
Earlier we saw just the selenium test card but this time you'll also see a year demo app dart zip.
So this is the application zip file which actually has our application and the UI test actually holds
are the selenium rated stuff which is gonna be used for executing our test.
So this is how we can actually do the things off deployment in the boot process began.
Also do one more cheat here we can create selenium test to run and see how it actually works.
We can extend the same thing for our release cycle as well.
So what I'm going to do is I'm going to do an edit here and then after this particular zip past been
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
for test and you can see that is something called us versus studio test.
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
copy this guy I'm going to paste it and I'm I know I know that I have something called s selenium or
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
this because we'll need then it'll make the test session running an interactive mode so I'm going to
do that I'm going to leave the test platform as latest because I actually have some sort of 20 19 installed
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
going to run things in parallel as of now and I'm gonna just add that and you can see that it has added
things for me or here.
So I'm basically going to run this and maybe I don't do required this particular search folder because
sometimes it won't work expected so I'm just gonna remove that and I'm going to hit safe right.
And then I see this again.
And now if I tried to run this what would happen is it is going to burn at the exact same thing which
was happening before.
So it's going to run the run the build process then it is going to reply the it's gonna create a zip
file and also it is going to run these selenium tests that we have in our repo and then it's going to
run that for me in my local machine.
Of course it is going to fail.
As of now the reason is because it has not deployed in my internal information so yet.
So that's why the test is gonna fail.
But you can still see the flavour of the test running in my local machine.
So we'll see what's really happening.
So let's go to the bullet came
and you can see that the execution is happening right now it has dared to publish and then the V.S.
test.
I was expecting the test to happen but I don't think it has really happened here.
So let me see what has happened and it says that it wouldn't be able to find the matching assemblies
which is nothing but the selenium data.
So I'm just going to go back to the bird again.
I know what is the problem basically.
So if I do that I did.
So here you can see that this particular slash is making the difference basically.
So we need to have this particular input to be a little more dynamic.
So this is not the way I should be looking like.
So I'm basically going to be doing exactly the same thing but in a different sense.
I'm just gonna have the input like test Assembly version to set any of us first and then testing out
and test adapter and object and then I'm just gonna hit safe.
I will also add the search folder which is something required and then I'm gonna hit run.
So this way it is going to be running the whole things for us.
See what's going to happen.
Now you can see that it is currently running the dominant bird release.
And I would expect this time something sure to happen for the obvious test.
There you go.
You can see that it is actually running the selenium test for me.
It has opened the browser but it has closed that.
And the reason is fine because we have been trying to run the whole test here.
We're just trying to see if that particular Chrome browser is at least card and it has opened or not
I could see that that's actually happening.
So now if I go to the bird and I go to the summary you can see that it actually shows that the test
has got failed.
So there is a nice report here saying there is a total one test and it has got failed and it has like
zero percent of passing rate just fine.
And also shows that doing the execution there was something wrong and it was not handled.
So there is a window.
Ed reporting do not show you a not set window enter dialog pops up in the middle that the UI test execution
then the test will hang.
So right.
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
can see that the same report comes in for us like what's really happening behind the scene.
And once I click that test it also shows me that there is no such element to locate which is fine because
as I said before our application has not been deployed yet.
And that's the reason the test is currently failing and we could able to see that this is going to be
throwing us an error which is fine for now because in our release cycle or in the released pipeline
we will see that this whole test will actually pass.
It won't be complaining as these kinds of matter.
So that's it guys is how we can actually add the build a pipeline to have the selenium test as well
you know the next video will do exactly the same thing but I'm going to show you the taste of the classical
pipeline instead of using the modern Jamel pipeline.