In our last video we discussed how we can run a test using the test plan.
Today we are gonna be talking about the low testing and once again this low testing is something just
kind of a test that you can do for low testing your application.
And once again there are some costs involved for the low testing if any use number of original users
and things of that nature.
But I'm just going to be showing you a very quick demo on how to work with a load testing off your applications.
I did a load testing of my yay appetite saw me dot com website this one which is like yay employee app
which I have used in many different causes of mine so you can see that the application by itself is
kind of very very slow in terms of the loading but you can see that the average response time for the
application this one is gonna be like two sixty point four millisecond which is kind of true and they
use a lotus just twenty five and their records per second is like forty three point four and you can
see there is no error anyways and you can see that this is the information that you get when it tried
to execute that and there are some charts as well he shows you that performance throughput and tests
and errors and things of that nature.
So you can see all sort of stuffs with the load testing of your application.
So if you going to do a load testing what you need to do is to see what sort of tests that are going
to be testing with are you gonna be doing a visual studio test.
So you're going to use the Visual Studio test which means you need to have load testing created in this
whole studio enterprise version or if you have has UDP archive based test which is something but the
HA file so you need to upload the hard file as well or you get if you have a patchy Jimmy to test.
You can also import the Jimmy test here guys which is really really cool.
So you can do that stuff as well.
Or if you have a you are the base test and this is what I'm going to be showing you where you can just
specify that you are left your application and it's going to do the testing for you.
Pretty cool right.
So I probably am going to do the testing of my local host and then I'm going to say load testing the
local app and you can see that you can also import the harder file if you have.
I don't really have one.
So I'm just going to leave it as it is and this is not even a kind of perfect low test which I'm doing
but I'm just going to go to the settings and you can see that it's going to ask you which provisioning
agent that you're using.
Are you going to be from South India China.
I don't deny that and these are the locations that actually have all this stuff and you can also see
that you can use the self provisioned agent if you have one.
And again for the self provisioning agent you need to install the on prem load testing agents for that.
Again that's gonna be completely out of scope of this particular course.
So I'm just not gonna be doing it for now.
Maybe in future we'll be adding that as a separate section so I'm gonna go to the app scenario.
I'm not even gonna add in these scenarios in here I'm just gonna show you the greatest feature the load
testing has got to I'm just going to run the test and once I hit the run test you can see that it is
gonna show you that the load testing is actually queued up and once it is cued up meaning it is gonna
wait for anyone off the available test agent and then it is gonna pick up that particular agent and
then it is going to start testing our application to again see that it is acquiring the resources right
now and you can see that the load testing is currently running and you can see that there is like failure
across up like hundred percentage.
The reason is because our application is kind of a local host and the local host actually means that
you need to make your application to be static IP or something like that but since it is kind of my
local machine I don't really have specified the static IP of my machine.
I will always see like lot of failures this time and which is gonna make sense as well because that's
how things will actually work.
So I'm probably gonna just leave this for now.
But since we have already seen the report I don't really want to show you how it is gonna be for the
local test.
So basically if you and run a test within your local machine you need to either go to the IP address
of your off your machine which you can find using my public IP and then you need to map this with your
eyes so or so that you can run that but I'm not going to be doing all this stuff right now but it gives
you an idea of what's really happening behind the scene so you can see that it is a hundred percent
failure which does make sense because it is not going to be running with the local machine but now that
you can see that it shows us as charred and diagnostic informations and the logs of what's really happening
with you or with your test in your application and also you can download the page requests and stuffs
from here plus it guy it is how we can do the testing with our test plans in a judo ops services.