Welcome back to my fifth lecture for soap UI, simple object Access Protocol user interfaces. Okay, so this is our fifth lecture. So back in fourth lecture that was a story. I mean, for me it was history. So, what we did was we executed MS DOS script. Remember, you know we did for numbers $2 and numbers, two words.

Just sweet go back there. And we also did assertions. Let's open that particular script. So, we also did in our assertions here. So, here is the number it converts into dollars, okay. That the whole concept of the of the web services action, wisdom So, work I did was Then and you know, I executed it and it showed us $10 and movie asserted this assertion remember in so this is an XML file, this is a raw file and we put whoops so this was so you can add a lot of features from here, okay.

So supposed to be something is soon here. Okay, so school exists request. And we did. Yesterday we was submitted a request. And we also went to this logs. Okay.

So these are soap UI logs and we got the superior logs. This error server knows some reason servers are still there. So he needs to get the logs. And the T bar. Log doesn't show anything memory log. Despite of from at this point of time, we don't require that.

I'm going to move to last Oh, says the reason why I amaze to stay sticks. Okay. So what I was doing right where I was And was pointing into the towers not using my desk. So this is my distance, you cannot put assertions for assertions and reasonable assertions of things. Okay, great. So it This is the real test case.

So you can put assertions only on your test. So, here in a C 100 that's fine. So this is my assertion and I ran this one and my assertion gets it's doing so even just supposed to be returning here, a spool up here. So I hope it's still running. For some reason it's taking too long. But uh, you can only add assertions only in the test case.

What do you have you created Okay, you cannot do that in the seat What's going on? Oh, this is beans. You could add assertions in the actual script. So this was the actual script, which I do get. And I was trying to see this injury in a way this assertion. Okay, so this is something happened to it does catch completely, probably want to probably restart this one.

Um, so, you know, we could Yeah, it's really stuck. And I really started it's actually running it but for some reason, it got stuck in Why don't we start to see this stimulus? So that was, that's what I was doing in the wrong way. So I cannot add assertions in the script. So you have to have a session discuss. Make sure you move that one.

Okay. So we were looking, there are a lot of options for the assertions. See here for go here. Here you go. All right. So this is my this case.

Expand this. And first we'll run this first tables. Okay, good. Nice ran successfully. Now here, yeah, there are some things going on. So assertion is valid and you can see that so if I change this when we were so cool thing we did on this right.

Let's talk about Oops, okay, um, you have a lot of assertions you know you can put recently used properties if you have Jason count etc. So what exactly is this assertion? We discussed this today though, but assertion is kind of check point you're checking that is there in that script or not? That's all we are doing. That's called assertion compliance. You know, do you have any so far but something script assertion, if you know, the script, groovy script, we know you can use groovy script, SLA, service level agreement, all the things, JMS Java You know, this gem is harmful and JDBC is under security.

So, we did a lot of things here. So my whole point was to you know, to show you how to add this assertion from that is very important topic for the so boi The reason because the Running is simple. Anyone can run the script, provided you have the script and provided you know what you're doing here. You want to append some values here, you see here, you're appending values, and you're getting response from the server. Script runs. If you see here, this is where files 23 you see them, and you have this log, either do yourself a favor, make sure this is this File, Export this file to dot log file, make sure dot dot log file and make sure if you have any issues you have to question the developer or if you're if you want to be a developer, you can see this large and see what's wrong if if anything is wrong here.

Okay, so make sure all this is good. And then you have to set an alarm clock and memory locks. We will talk about that later. Okay, so that's what we were trying to do. Now we have to dig for wet before I'm sorry, script. Okay, let's open the script actually open the script, you have to open the script script.

This is a script for numbers, do words. And we did this to go ahead and click on this to see the here in Toronto. And it's this number is changing into figure. Okay, that's what it is doing. So numbers, two words. That's all it is.

And we have this assertion of 100. And it is we did know I did something some mistake, or give some spelling mistake, because of my spelling mistakes. That assertion got failed. So that's how you mostly it's not necessary on the assertion to get past because this is a very simple script. This is super simple script. I mean, real time it doesn't exist, this simple script, but I'm just showing you as an example, because you have to start from somewhere right?

You start from zero From 01 to three, you know, this is the zero this is 08. Find your money. This is a joke that, you know, wisdom is not this simple. This is the easy one. It's like converting into hundred to 100 and the sauce. Okay, okay, good.

Let's do what let's do load testing in this. Okay, we'll do load testing. And probably in the next class, we'll do security testing. So this is the full picture. And I be an hour dad. Oh, I'm sorry.

It's 55th lecture and I will there is no attachment. There is no handout for this one. Let me check this year there is only for functional testing in experts. I will be adding that one. So there is no handout for this one. But here you will.

This is pretty simple. So but for low testing as to low testing, it's it's very simple. It's again running the script But running the script, but the way you run, if you see this icon, it has become from grey to green color. If the assertion gets failed, it becomes in red color if you notice those things, okay? Probably if you have these graphs the gap so hope is supposed to have some kind of graphs. No graphs, unfortunately, but normally, we don't require any bells for this.

Because it is not something we are just testing wisdom. Okay, this is this is. That's it. I mean, that's how you do it. But this is very simple script. Technically, you don't have that simple script.

Okay. Probably a little complex one, which I showed you yesterday. This is a little complex. Discussion screenshot This is a bit more complex where you put the IP address in You know all these things and and then get the response. Okay, this is medium complexity, we go to high complexity decimal moment once we finish this class, okay? Probably the next class of future plans but by hopefully by today we'll end this or probably disrupt the planning tool, because tomorrow I have another meeting So, okay, so here what I'll do is selling this load test I'll do load testing load testing for what load testing for numbers should dollars.

Okay, so what I'll do is go and double click it. Let's do this. No, it's not working. Okay. Go ahead and click on new load test. See when you created this low low script, remember you have this checkmark always do load testing for that.

We didn't do that. Remember? So what do you want to do right now since we didn't do that, now we have to do this new load test we'll put as low test one. Okay great. Um, these To be honest, this doesn't have any you know, many graphs but we'll do this okay but you still is okay. So low test and for this we have this Lotus one okay.

So what we are doing is the thing we made simple so we are we are doing four numbers $2 Okay. So we are taking how much time to what is low testing Exactly. So you are identifying the bottleneck of an application. So what you are doing you're doing you know delay of sweetener a lot of parameters simple burst Rate Variance, we'll go for simple for now. Test delay, thousand and random point five limit 60 seconds. That means it runs for 60 seconds.

Forget it. Good. We don't want more than that threads five threads. Okay, that means it's kind of iteration. Okay? We have load testing assumption students, that's fine.

Okay. So now let's do this. Which test case I'm running? How can I add a new test case? No. Okay, so now let's run this once we run this, so it's running.

You see this is running, let's say you mean you don't have to do anything here. Here you see this time 17 18% completed in this number says chaining minimum and maximum and the average in the count bps hurting its bytes and bits per second and the error and we know this, this is not that harmful. Okay? Um, work we do here it is. Okay, here Do you want to see this movie live? Okay, this is what you want to do.

When this is running, I'm limiting for 60 seconds, you can limit for any number of things, you can go ahead for 60 seconds to go 4000 seconds or so on. But in this class, I'm just waiting for 60 seconds. We don't need more than that. At this point of time, you want to see this graph. This is running now this has stopped 60 seconds is over 100% complete. Here you want to can you can be correct.

We don't want that. Okay. Now this is the memory lag. You want to see how much is allocated how much is used. Okay, that's good. Anything new here?

So this soapy white blobs will be there. HTTP locks will be there. Now let's see this message. Can I pin this on this message is cannot do any work here. You say that it ran for one minute. too, that is 60 seconds and ended with one minute.

Minimum is 259. Maximum is 1497. So what it exactly did he put the load? So here's the diagram, let me do some background on this. So what is this load testing? So what happens is, whenever an application, let's say take, let's take an application, let's say thousand people are logging into that application at that same amount of point of time and that amount, point of time, thousand people are lying.

How much? You're getting stressed to the summer, you know, it's okay. The stress testing and you know, low testing are two different things, or stress testing is you're also creating a database query. So here we are just doing load testing nonsense test, okay. Sr, sr, much more complicated, and I think I don't think this has that option here. So that's it.

I mean, this is how you do This load testing but but here's the thing who you want to check it out the logs I'm sorry not see of course you do. This is the two logs which you have started it and which which has ended this based on this time how much time you're given but thread per second so we go to it for a second. It's good. Yeah, I want to export this. Let's find out let's let's do this on my desktop and see that load test. I don't know what files it is safe for the students.

Okay, oh, so only these two things will get saved. So it will be XML file dot txt will open to this dot txt. Yeah. So the only thing Okay, I got this. So what happens is Hear this only these two things are getting saved as root. So you can save as Excel.

A birdie, there are a number of low testing, we will see this if there are four, there will be four different columns. And sorry, four different rows. These are the columns. Okay? So that's how you do it. And let's take it out this graph.

This total, I mean, this is how the graph looks like, Okay, this is the trade calm. And the average is in millisecond error count transaction per second and bytes per second. Okay, so the total and the resolution is data. Okay, we'll go to Google commercial admission how it looks like. Okay, great. So this you can export it.

Let's see. Okay, let's find out. I want to save this as the hub. To JPG file a BMP file. Let's see. I did some mistakes next to this, so everything gets stolen me and unfortunately the last option is save it.

So, you know, you can take a screenshot, you know, take a screenshot just like this. And, you know, just use this is a big deal. Nope. So I don't worry about this one. Okay, let's take a screenshot and open go this flood of data. So this is an int t seconds.

This is the data it has sent and received an award over this hearing of this thread how much call Order the minimum Max and average last our TPS bytes. So how much enter and how much is received? It's shown here. Okay, this is a good, you can change that into x dot txt file and see that. So that doesn't help. This graph is not actually, you cannot say this club, I mean, it's not like interactive it used to screen and save it in paint.

That's the best thing you could do. Okay, so that's the total total resolution on the data. Graphs we should change. So it didn't, there's no refresh rate. So that's how you can do it. I mean, you know, that's how for 250.

Okay, so this is one graph you could do. So that's the statistics graph. Let's go to history statistics graph. So this is Average, find out. This is a thread counts how much thread counts and rates you can use TPS. Okay?

Resolution 250 dilution good. Error thumbnail, we did have a bit per second, I'm sorry, bytes per second. So this is how you get the graph. So this is a statistic history. So in low test day, there are much more things to do than just running this. Of course, you have to run this and get the data and plot the graph.

Okay, plotting the graph is very important here. In soap UI. You don't have this option of plotting the graphs, unfortunately. But if you are using a good tool, like modelling that does everything that even though it does stress testing for you, but this has limited functionality, but still it does. You Have the statistics graph. And you can export it.

I mean, you can, you don't need an option, just use this print screen, and go ahead and use this paint and this use this one. And this is you don't get better than this, use this one and I don't care. I mean, I don't care, I don't have the option to say this is the best way to say, right. Okay. You know, this is how you save your graph. This is the better thing, okay, or you won't need any savings from this export option.

What it's for is only exporting the data but not actual graph. Okay, so I'm always bothered because I can take a screenshot and, you know, save that graph. So that's pretty much for load testing. For this this was for number $2 Okay, number sugars, okay guess what you know what? This total okay guess what I put it as a handout for you because if you want to know this graph Okay, so this is how you do it take a screenshot, you know probably in it poor version you might have an option to export this as bat file or PDF file but in this particular scenario you don't have this. So, low testing, load testing, so only one graph unfortunately, but there is not one graph is large graphs for load testing for number $2.

This was for number $2. Okay, so num $2. Okay, and I'll save this file and put it as a handout all low. It may not make sense for you at this point of time. But when you're running this one, it might make use of it. So this lecture Five, six, so this is the ground for this, okay?

This is that simple. You won't have to worry about any of some graphs is very important. And the data of course, the data is important. So we're going to export this data for 60 seconds. So what I'll do here is for you, yeah, export this and dot txt or you won't portal dot CSV. Let's see if I if this works on CSV file.

Probably true. Oops. So this actually did only for to open issue in my system to do worry about it. Let's see. But if I want to see this graph and I want to I want to export it Okay, so this is for my end, okay. Worry about this.

Yeah, this did good analysis. This is the data for the graph. Okay. That's fine. So this looks good. So what I will do here is a low test data with four This 115 out scuffle, that's fine.

Let's find out how this is no tension. This is notice data. It's see. Um, so here, this is the this is what happened when we ran the data. Right? So this is very important data from this, you actually can create reports.

So creating an import, and creating a graph like this movie, you know, is a different thing altogether. That is something which I'm not showing in this class. But also this as a handout for you guys, so that you might have some idea on this sorts we are doing here. Okay, so this was low testing that said, I will not that's it. It's kind of we ran only for 660 seconds, but he don't have to be 67 people ran for hours, clear. and figure it out.

Because if you're running for hours, the data will be more the more data the grass will be more accurate. Okay, the grass will be like, you know much more accurate graphs and the error account will be there and learn more information. But this has only one graph, unfortunately. But it's not just about the familia de Gracia MOOC on memory, how much memory it is taking when you're running. This is all have to be taken into consideration when you're trying to load testing. And you're not putting any checkpoint, you don't have this transaction time start transaction time in transaction time.

You don't have anything like this in soap UI. That's a little bit of a drawback. So that's why people prefer loadrunner. loadrunner is a tool to test the load testing. But nevertheless, this is a tool for laymen, people, you know, to people who can effort. This is a good you can get a lot of data, you got this data, plot your own graph, you get even the graphs, just take the screenshot.

That's how you can do and memory, make sure you take a screenshot of the memory job, that's fine. Okay, so you can use this as the load testing. This is how load testing is done. Okay, so that's pretty much to increase the start and end. Okay, so we'll do one more minute load testing actually. And then we move move on to security testing.

Okay. So we need numbers to close this. Now we'll do four numbers, two words. Okay. So I'll go ahead and right click on this. Okay.

Create a new and say load test one. Okay, great. Now I'll put threads as dead Stop finding just making little complex strategies simple we don't our variance I will go with means we'll go to simple does delays thousand random is fine five to this to this default 60 seconds, I get a lot of data six will not go for too much of time. If you have too much time you can do that we can put as one hour or something but you don't want to waste too much time in this unless you're really doing some low testing part in getting grasp for it. But you know, you don't want that one. So go ahead and click on this and it's running see here 4% open the memory lab.

See the memory. Okay, see the data changing. So the average last call we are running for this 10 threads. 10 threads gets you more memory Usage Sr. The set of memory is increasing. Now, we are just testing the memory we are also doing a lot of things here we are getting this putting low and how much memory from server is utilizing.

See here. This graph is changing a very spike a lot of spike here. All right, um, this is complicated. And you're getting a lot of data, this whole data 35% is completed. And this is how you actually noticed it. And that's it.

This is what you do the whole day, actually. So, and this let's say this guy named it now this is the lock take the screenshot, no, misinterpret no photos for ease of convenience. Just put same day as a number Two words. Okay, and we'll see this in desktop. And here. Okay, great.

Let's just hide that word and see the graph. Let's view the graph. Okay, this is the graph for 60 seconds. Okay, fine. We'll just I'll take a screenshot. And we'll see we don't need the pro version for this program and I have this feature option.

So here, I'll just use this whatever is required for me not a thing. And we'll use that as safe as load testing for num, two words tonight And no forget the data export this file into here. data. We know it is a data. Now you can words numbers to words and save it as the tiamo 195 volts, that's fine. So this is a good as a handout on this, you know?

So this should be good. So this will be a handout for you, just in case you want to view this or how Iran you can use this same option right underneath your homework homework. Right is so I get negative feedback because they say like imagining assignment so this is your assignment. Yeah, of course I'm not doing any physical assignment but at this assignment do this load testing for Oh, we have a lot of web services, guess what free web services in various issues. Here you go. So we have a lot of test weather data to test your NASA and delayed shock treatment.

So we'll see if we get to go through that. Probably I'll go that one and show you all of them at once. And I will go pretty fast because you know what we are doing here. Okay. So that's pretty much for load testing. Okay.

So we'll go to the next class and see the security testing. And after that, we'll go from rest. Rest in oblivion application is probably similar kind of thing, but we Go to that. Okay, so I actually I was saying this one, I was redeeming the last. Let's save it. So it saved here.

And that's it for now. And, you know, I hope you liked this video, if you will. So this is your assignment assignment, run the load testing for for this, if not for this there are a lot of wisdom services that is in your handouts, use that one, run it, run with the test case and get the results, get the data out, plot the graph, that's all you want to do for the load district. And how the you want to see how the editor responds and how the spike of course you want to see the memory also, how much utilization of memory is used. You know, you want to go on and so that's your homework, okay? If you're not getting assignments, this is your SMS.

Okay? So that's pretty much for this class for load testing. I'll see you in the next class for security testing, you know, thanks for watching and see you in the next class.