WEBVTT 00:00.200 --> 00:05.820 In our last video we discussed how we can run a test using the test plan. 00:05.820 --> 00:11.370 Today we are gonna be talking about the low testing and once again this low testing is something just 00:11.370 --> 00:15.550 kind of a test that you can do for low testing your application. 00:15.720 --> 00:21.060 And once again there are some costs involved for the low testing if any use number of original users 00:21.060 --> 00:22.310 and things of that nature. 00:22.410 --> 00:28.710 But I'm just going to be showing you a very quick demo on how to work with a load testing off your applications. 00:28.710 --> 00:36.540 I did a load testing of my yay appetite saw me dot com website this one which is like yay employee app 00:36.600 --> 00:41.490 which I have used in many different causes of mine so you can see that the application by itself is 00:41.610 --> 00:48.090 kind of very very slow in terms of the loading but you can see that the average response time for the 00:48.090 --> 00:55.290 application this one is gonna be like two sixty point four millisecond which is kind of true and they 00:55.290 --> 01:01.860 use a lotus just twenty five and their records per second is like forty three point four and you can 01:01.860 --> 01:07.140 see there is no error anyways and you can see that this is the information that you get when it tried 01:07.140 --> 01:13.470 to execute that and there are some charts as well he shows you that performance throughput and tests 01:13.560 --> 01:15.540 and errors and things of that nature. 01:15.840 --> 01:19.850 So you can see all sort of stuffs with the load testing of your application. 01:19.980 --> 01:25.260 So if you going to do a load testing what you need to do is to see what sort of tests that are going 01:25.260 --> 01:29.000 to be testing with are you gonna be doing a visual studio test. 01:29.010 --> 01:35.400 So you're going to use the Visual Studio test which means you need to have load testing created in this 01:35.400 --> 01:41.070 whole studio enterprise version or if you have has UDP archive based test which is something but the 01:41.100 --> 01:49.200 HA file so you need to upload the hard file as well or you get if you have a patchy Jimmy to test. 01:49.230 --> 01:53.110 You can also import the Jimmy test here guys which is really really cool. 01:53.160 --> 01:55.390 So you can do that stuff as well. 01:55.560 --> 02:00.690 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 02:00.690 --> 02:04.860 specify that you are left your application and it's going to do the testing for you. 02:04.890 --> 02:06.070 Pretty cool right. 02:06.150 --> 02:16.550 So I probably am going to do the testing of my local host and then I'm going to say load testing the 02:16.590 --> 02:20.600 local app and you can see that you can also import the harder file if you have. 02:20.610 --> 02:21.880 I don't really have one. 02:22.020 --> 02:27.210 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 02:27.840 --> 02:33.120 but I'm just going to go to the settings and you can see that it's going to ask you which provisioning 02:33.120 --> 02:34.470 agent that you're using. 02:34.560 --> 02:36.470 Are you going to be from South India China. 02:36.810 --> 02:42.870 I don't deny that and these are the locations that actually have all this stuff and you can also see 02:42.870 --> 02:46.770 that you can use the self provisioned agent if you have one. 02:46.810 --> 02:53.060 And again for the self provisioning agent you need to install the on prem load testing agents for that. 02:53.110 --> 02:56.530 Again that's gonna be completely out of scope of this particular course. 02:56.580 --> 02:59.070 So I'm just not gonna be doing it for now. 02:59.070 --> 03:04.640 Maybe in future we'll be adding that as a separate section so I'm gonna go to the app scenario. 03:04.680 --> 03:10.020 I'm not even gonna add in these scenarios in here I'm just gonna show you the greatest feature the load 03:10.020 --> 03:15.420 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 03:15.790 --> 03:22.610 gonna show you that the load testing is actually queued up and once it is cued up meaning it is gonna 03:22.620 --> 03:28.350 wait for anyone off the available test agent and then it is gonna pick up that particular agent and 03:28.350 --> 03:34.200 then it is going to start testing our application to again see that it is acquiring the resources right 03:34.230 --> 03:40.700 now and you can see that the load testing is currently running and you can see that there is like failure 03:40.700 --> 03:42.320 across up like hundred percentage. 03:42.360 --> 03:49.890 The reason is because our application is kind of a local host and the local host actually means that 03:49.890 --> 03:54.660 you need to make your application to be static IP or something like that but since it is kind of my 03:54.660 --> 03:59.550 local machine I don't really have specified the static IP of my machine. 03:59.640 --> 04:04.890 I will always see like lot of failures this time and which is gonna make sense as well because that's 04:04.890 --> 04:06.590 how things will actually work. 04:06.930 --> 04:08.950 So I'm probably gonna just leave this for now. 04:08.970 --> 04:12.810 But since we have already seen the report I don't really want to show you how it is gonna be for the 04:12.810 --> 04:13.530 local test. 04:13.530 --> 04:19.140 So basically if you and run a test within your local machine you need to either go to the IP address 04:19.170 --> 04:27.990 of your off your machine which you can find using my public IP and then you need to map this with your 04:28.050 --> 04:33.600 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 04:33.600 --> 04:37.700 you an idea of what's really happening behind the scene so you can see that it is a hundred percent 04:37.770 --> 04:43.350 failure which does make sense because it is not going to be running with the local machine but now that 04:43.590 --> 04:49.200 you can see that it shows us as charred and diagnostic informations and the logs of what's really happening 04:49.200 --> 04:56.780 with you or with your test in your application and also you can download the page requests and stuffs 04:56.790 --> 05:04.040 from here plus it guy it is how we can do the testing with our test plans in a judo ops services.