WEBVTT 00:00.210 --> 00:05.760 In our last video while we were working the release pipeline we also did the selenium UI test automation 00:06.030 --> 00:13.530 and we also saw that the report was also coming with the runs tab as we saw in our previous video. 00:13.530 --> 00:17.770 So the runs tab actually showed us the exploratory session that happened. 00:17.820 --> 00:24.750 So basically it is not the manual test or any desktops run test which happened basically it is happening 00:25.080 --> 00:27.860 from our pipelines of releases. 00:27.870 --> 00:30.110 So this is where the test actually happened. 00:30.120 --> 00:33.450 And we also saw that report coming in something like this. 00:33.450 --> 00:38.820 And we also saw that it's all gone past which is pretty good and it should feel like we are doing something 00:38.850 --> 00:40.140 on the automation testing side. 00:40.140 --> 00:44.770 And we have some sort of track of what the test is actually doing. 00:44.940 --> 00:51.030 But now that we will go back to our test plan which is available within a year or ops and we'll see 00:51.300 --> 00:53.880 what actually the test plan is actually doing. 00:54.150 --> 01:01.920 So if you remember what we're trying to use this particular test plan in the early sections we saw that 01:01.920 --> 01:07.650 the discipline actually required some sort of licenses like you need to have at least a license or you 01:07.650 --> 01:12.640 need to have an exploratory test so to see this particular tab very with all the details. 01:12.720 --> 01:15.750 We now have the results in the runs. 01:15.750 --> 01:19.680 And that's the reason we are actually seeing this particular test plan itself. 01:19.860 --> 01:25.290 So you can see that now we can able to see what's really happening with our executions and things of 01:25.290 --> 01:25.800 that nature. 01:26.160 --> 01:31.740 But now that if you remember in our previous videos we also created this particular test entire feature 01:31.830 --> 01:33.630 within our feature. 01:33.840 --> 01:38.510 And if we just open this particular test the entire feature you can see that it is currently in the 01:38.510 --> 01:46.230 ready state and you can also see that this particular feature have eyes closed basically while we ran 01:46.230 --> 01:52.920 this particular this particular chicken and you can also see that it has a complete development track 01:52.920 --> 01:58.380 list of what really happened for that particular for that particular feature for the test and diet feature 01:58.380 --> 02:05.640 test case was belonging to this particular Google author mechanism and this particular Google mechanism 02:05.700 --> 02:08.730 actually was part of the feature. 02:08.760 --> 02:14.610 And once we completed this feature it also closed this particular test case and then you can see that 02:14.610 --> 02:20.880 it is completed kind of but you to see that we can also add some sort of test cases in automation so 02:20.880 --> 02:27.330 you can do something like a planned test case for the automation you can do that and also you can add 02:27.330 --> 02:30.870 some test to steps for this particular test cases. 02:30.870 --> 02:37.590 Again this is exactly the same sort of test cases that you can use in the BSD yes or in the Test Manager 02:37.620 --> 02:45.000 of Visual Studio which was there while Visual Studio 2010 released and it's exactly the same in combinations 02:45.000 --> 02:51.480 of the edited versions but just that you can now see that it has even more details of what really happened 02:51.690 --> 02:53.940 with that particular associated work items. 02:54.180 --> 02:58.770 So you can see that it's completing the pull request to us all of the work items so we also did this 02:58.770 --> 03:04.920 particular one once we completed that it just came in here and it also closes this particular test case 03:05.410 --> 03:12.060 so quickly tried to add a few test cases or here and we can also associate this particular test case 03:12.120 --> 03:14.330 with our existing test or something like that. 03:14.730 --> 03:19.980 So you again See you can also associate the automated test if you want or here. 03:19.980 --> 03:24.810 But since we don't really have any I'm not going to be assigning that and now I'm going to say like 03:24.870 --> 03:41.090 open the application navigate all the menu items click the home page verify if the home page exist name 03:42.010 --> 03:44.420 home something like that. 03:44.430 --> 03:50.630 So you can see that if I put this particular at home you can also get that particular stuff in the pad 03:50.660 --> 03:51.600 meters or here. 03:51.600 --> 03:59.520 So basically the at home it turns into a perimeter based value so you can just say at home or something 03:59.520 --> 03:59.820 like that. 04:00.060 --> 04:01.350 So that's what is this. 04:01.440 --> 04:04.810 This particular part of me is going to be doing. 04:04.890 --> 04:07.640 It can also say like new home. 04:07.680 --> 04:13.950 So it's going to run the test for like two times pretty much like how the cucumbers example actually 04:13.950 --> 04:14.880 works. 04:14.880 --> 04:16.890 So I'm done with all these things right now. 04:16.890 --> 04:19.270 I can also do save and close. 04:19.290 --> 04:22.950 So this bigger test is right now ready for us to do the testing. 04:23.010 --> 04:28.170 So if you're going to run this particular test for a web application so you can just run something like 04:28.170 --> 04:35.300 this for the web app and you can see that that test comes in here for our test case that will be running. 04:35.370 --> 04:39.840 And now you can also do the side by side test and see what's really happening. 04:39.930 --> 04:44.380 So basically our application is deployed in the local host eighty one. 04:44.430 --> 04:49.320 So I'm just going to be testing this as if like I'm testing the application instead so opening the application 04:49.350 --> 04:54.720 is working fine and then getting to all the menu items. 04:54.870 --> 05:00.520 So you can go to the home just working about is working and contact is where. 05:00.530 --> 05:03.530 So I will say that this is working fine as well. 05:03.650 --> 05:05.630 And again I'm going to click the home. 05:05.750 --> 05:08.420 So I would say that this is working fine. 05:08.420 --> 05:12.320 And verify if the home page exists with the name at home. 05:12.320 --> 05:13.590 Of course it doesn't really exist. 05:13.610 --> 05:16.460 But I can still say Yeah it's working fine. 05:16.460 --> 05:17.480 I can save on close. 05:17.540 --> 05:24.680 But if for some reason if I feel like that home is not there with the at home or something like that 05:24.740 --> 05:31.420 let's say for the next iteration I'm going to say everything is working fine just that for the home 05:31.460 --> 05:40.160 it is not that if the name s new home that I'm going to say this as failed I want to say no such home 05:40.160 --> 05:42.160 page exist. 05:42.380 --> 05:50.960 And also I can take a screenshot and even I can create a buck to an existing bug I can attach that and 05:50.990 --> 05:57.500 I can just say like it is not working as something like that create bug and you can see that the create 05:57.500 --> 06:04.700 bug window is gonna show us a pretty cool window here and you can see that this is this has got failed 06:04.730 --> 06:05.860 as well. 06:07.600 --> 06:19.430 Home page fast no intended value add this to the development. 06:19.580 --> 06:28.050 So I'm just gonna say that this is found in the branch in the master branch and I'm going to hit OK 06:29.180 --> 06:35.030 and you can see that I can able to associate that with the master branch and also you can see that for 06:35.030 --> 06:40.070 which that pattern is gonna be assigned so it's gonna be basically for the Google auto mechanics I'm 06:41.150 --> 06:42.430 just crazy. 06:42.440 --> 06:48.230 You don't really have to do this way and I'm gonna just save and close this guy and I'm gonna stay in 06:48.290 --> 06:53.170 close this as well so you can see that this particular test has got failed so the next time I tried 06:53.170 --> 06:58.910 to run this piece up test cases you should make sure that particular issue has been resolved on something 06:58.910 --> 06:59.590 like that. 06:59.840 --> 07:00.310 Right. 07:00.350 --> 07:02.440 So you can do all that jazz here. 07:02.450 --> 07:08.960 So for instance this is like ready and now I'm gonna be running this particular test case I can just 07:08.960 --> 07:14.810 run this in the web browser once again and I feel like this particular test case is not working. 07:14.810 --> 07:16.360 Final thought on your problem. 07:16.370 --> 07:21.060 I'm going to go next to the next iteration and I'm going to say OK. 07:21.080 --> 07:24.620 The new home page existence will save and close. 07:24.620 --> 07:30.320 So this way that this has got past and now if you just open this particular guy here you can see that 07:30.320 --> 07:37.520 there's just not an issue now and I can also get that closed which means the test has successfully completed. 07:37.520 --> 07:37.700 Right. 07:37.700 --> 07:45.080 So this how we can do a manual testing with our test to plan off I sure do ops and we can also see the 07:45.080 --> 07:52.730 automated test over here and also we can see the exploratory test over here in this particular run as 07:52.730 --> 07:54.380 how we did in our previous video. 07:54.620 --> 08:00.050 So you can see that for this particular test and there is like need in investigation and there is a 08:00.980 --> 08:06.920 there is this parentheses it says like manual testing and you can see that report like what's really 08:06.920 --> 08:10.580 happening and why it has got failed in the report. 08:10.580 --> 08:17.240 And if you see this guy that run I.T. this one has got passed and you can see everything is working 08:17.240 --> 08:18.380 fine as expected. 08:18.410 --> 08:25.100 So you can see that I'd like to test runs no one has not failed and one has got past right. 08:25.190 --> 08:25.760 Cool. 08:25.760 --> 08:30.080 So this is how we can work with the test plans and how we can do the mental testing. 08:30.260 --> 08:35.330 And again if I can run this in for the desktop you can click that and you can see that it is going to 08:35.330 --> 08:41.420 ask you that you need to install the desktop application so that you can test the desktop applications 08:41.450 --> 08:41.870 as well. 08:41.960 --> 08:47.180 But since I'm going to be showing you the desktop application I don't think this really matters for 08:47.180 --> 08:49.420 now but you can still do that as well. 08:50.250 --> 08:50.840 So that's this guy. 08:50.870 --> 08:55.970 This whole began to work with a test plan you know next video we'll see how to work with a load testing 08:56.100 --> 09:00.710 just available for free for at least less than 250 virtual users.