Okay, so we are almost completed any sort anyone have any questions so far for this whatever I like visual variables are based on your knowledge training, other people training. I mean, I mean, the subject Any questions? Yeah for the ETL right for you have any questions in the ETL point of view? I think. So if it is SQL I think Sanjay and PIP nominee Kim Ray It very so concept and think germane to contact title. Okay, so let me give some brief.

Oh, right. That's a good catch. Okay. That's good. Yeah, no, we didn't cover this requirement traceability matrix, right. Okay.

I'm explaining surely for some reason it just went okay. So this is a concept. Okay. requirement traceability matrix, we know you just No, it's just a definition. So what does it happen right in requirement traceability matrix, all the requirement should at least match one test case or I'm sorry I just told it other way it's not it's not at all the cash cash should at least match one requirement okay. I just told it another way this all the test skill.

So, whatever the test cases here written right should at least match one requirement that means, if you have 10 requirements all that tend to come in with our test cases okay whatever they choose as you have written, so, you will write test cases right. So, when you run the test cases you have to match up with the requirements. So, this is this concept is only in waterfall methodology because invertible methodology that you need okay. Ah PNM in even in a jail Okay, they're in HP mmm let's see if that be able to access but no no more working. So let's see if I can add our experience I just no matching there's all these edge cases already. Return to the requirements or you have all the requirements.

You'll match that working Okay, so that's what you that RPM is the wrong issue all the discussion should at least match one requirement. Okay that taught you working on good So this is the one without the next wow Okay, looks like people like more defects models and test cases that I see more defects and test cases with very long defects I guess okay. Okay, so good so you guys might have been got used to it right so you know how to like know when to fix I test cases so we should be good okay the issue when you go into practice you need to find out what is your What are you working on see even doesn't matter even if it is QA ETL software or anything you just need to open defects That's what you are hired for right as a tester way too into open difference, that's what it is.

But make sure you don't do too much. Okay? Make sure you don't open too many defects. before running Of course you need to talk right you need to first talk with a local someone or lead or if you are reading to check with developer or you know check with the scrum product owner Scrum Master. Okay. So make sure you do that you cannot open the snack and as always, you know, just make sure you know you found an issue.

Of course it might be issue it may not be issue we don't know. See in the comments. Everything will not be there. No, you understand that that there will not everything in there requirements you need to make sure that the issue is is that say that A genuine issue or it's a feature. Okay, my vote will be a feature we don't know. So I didn't understood your question properly.

Hey, anybody have any questions? Yes, sir. Can you give me an example of the the tester said we have we had we all did the defense on said we all do the things consuming the example of the Crystal Lake I mean, I didn't understand one example of a test of like, You mean like opening defects or reading on exactly what do you mean? So like, finding a tester, but Testing, testing the websites and finding the defects. So, now you just like we found all the most of the students, we found the defects, right? So, yes.

Can you give me an example of testing? Yeah, I mean, this is why that's right. I mean, the testing like completely like you open a W, you open a web application, just like you did, okay. You find issues and find out something is missing, you know, something like that. There's a missing in mismatching product or mismatch in the quality components. You know, something Are you know, Suddenly, for example, like shipping and handling fee to the down name.

So testers, yeah, so tester is something like after you do something and you find the defects, there's a tester, but if there is something, or if there's a defect already that you can see, without doing anything, so there's a defect. Right? Right. Yeah, we don't know if you haven't. Yeah, that might also be, you know, finding that issue and reporting it. Normally you will report it, don't open defect.

Okay, if there is already an issue, and you found out that it's an already issue and there is a defect, then you don't have to do anything. Because, you know, they already know that it's an issue and there is a defect number open with that. Making Yeah. Okay, so yeah, so let's know. Okay, good. Let us know.

I'll be quick and fast. Okay. To explain once again let's just go through the slides and go back to good. So, so discuss few of the interview points we're doing okay. So what are additional right various types of testing. So we have various types of testing, okay.

So this is like you know, as I said it is a high level testing is all on high level, you will be doing mostly if you aren't as a QA or if your QA and your testing automation We'll be doing legging functional testing functional testing that is performed inside then it's a non functional testing. Okay. So this is the black box testing, black box testing, this is making a visual requirements and functionality, it is a high level of testing. It's a high level testing which is done by the testers. Okay, it is based on the requirements and functionality of an application. Then you then we have white box testing.

So this testing is built on the code. So normally This is done by the developers. Okay, there's also one more like blackbox testing, okay, it's also called a glass box testing white box testing and this is done by the no by developers normally internal logic internal core of an application. So what we see is in web application you see only buttons and you know, you don't see actually the code. Then the code behind that right there's always a corner even if you're using this power find as a co band, but you don't see that code. Okay, so that's not that is black box, is what you see in front end or black box.

Very see something which is a code that is white box Okay. And then you also have gray boxing which has worked, you see some code and you see no token on television that is that is both black box and white box. So, that is normally done by the either by tester or developer you know Africa requirement how they want to do okay then you have like unit testing this is this is also done by the developers Okay, these are done by the developers and this is also module. So, in that zone you are actually testing some particular module, okay the unit testing, then you have in figuration testing where once you all the modules are integrated, so, you have each module somebody is testing like, you know, cortex for different things and they are integrating that all modules into one application. Okay, and after integrating that, you know, you want to test that the snowboard is broken, because all core is different it to somebody, some developer as bugging that some developers work in this to know all this And they are integrated that and made sure that after integration, you know, our integration there and something else didn't break up.

Okay? So that's what we want to test forget that integration after integrating that everything into one website now to test okay integration testing then you have to do incremental integration testing, okay. In the incremental integration testing, you actually do not want implement increments name is a name except that it increases. So, you know, that incremental integration testing. So, new models keep on coming up, you know, keep on the keep on adding new new models and you know, you keep on testing and so that will be an incremental integration testing. Then you have functional testing, functional testing is like content distinct.

Okay. This is where you test an actual application. So it might be an web application or try and application Okay, so it can be either anything that is functional to What is functional testing the functionality of an application? Okay. Testing means you know, you're actually testing the functionality of an application, what is the functionality? functionality can be anything?

Right? It can be edit box, check box, you know, static text, dynamic text, or, you know, URL images in our drop down box, checkbox, whatever comes to mind, will do our job buttons, no button box, you know, all the stuff, whatever, it's new and new, they invented, everything comes into functionality, okay, and the functionality, testing the functionality of an application. And then you have like, system testing, where you actually change the entire system that includes the oise. Okay, that includes the oil of any system then you Okay, so everything comes under threat, what are what are they contributing? Okay, you have to know which choice you're working on, like Windows Mac or Linux or 10. You know, you have again in there always have a browser installed which closure here.

Sorry, which browser, Google Chrome, Firefox, Safari or no opener, I don't know the unique ID and then you have which version you're using for that browser obviously everything that is that includes everything right which application again you are using that application itself it has a different version, okay, that browser has a different role in operating system has a different model. So, all this thing is called system testing. So, this is not no scientist specific it is done by a team member, okay system testing. So, these are the pretty much high level very high level this Okay. And then you have like an end to end testing for end to end testing as a QA point of view like you know, testing everything from no right from functionality performance, you know, low stress and what else many regression you know, everything that is called end to end testing that means, what you have started and mature and from one point to another point without end to end testing, but if you are considering as a whole As a tester as a job of a tester, then it includes everything.

ETL No, then you have Informatica. If you use Informatica Informatica jobs, then you have no third party tool, then it auto says jobs and you know, and then you have that data loaded, how much data is loaded, how much data testing you have done how much then use it showing the web pay appropriately, those are the two that is end to end testing user point of view, then it's limited, but if it is, then at a point of instability in the in the ETL point of view, then exam qL also included in that goes into part three, QA is a part in the ETL. Right. Okay, then you have sanity district, okay, sanity smoke testing, is one more smoke testing where you actually test the random district. It's like every once the build is once the build gets loaded into that and you just test Okay, just so randomly, suddenly you get a you got a website and then Listen, hey, do smoke testing today's so then you know what you do is like you know, just test randomly and say okay, you know it's good week I can proceed further, but if you found an issue in that then you say this application has failed smoke testing, smoke testing itself has failed that means you cannot proceed with normal type of function testing because it has already failed smoke testing.

Okay, because, you know, you we have tested it randomly and it has been failed. Okay, so I'm sorry. So that is smoke testing, okay. So everyone uses So random district where we will actually randomly notice that and if you find an issue, then you may say like, you know, everything will be listed. And you can proceed with the partial listing, okay, then your sanity testing to telega on version one affair, and so I've given you real time example for this right last time. So I've shown you how do you do that?

So once you Okay, we didn't do actual any testing that like I showed you some changes in right. I went to open a Firefox browser, right? All these features were there, right? I know there is something different here. The fonts were actually different. And you know, see this, the font for the Google Chrome was different and then, and these modules were no lucky.

No icons were good. Go short it has become sharp. But then you know what I did is like you know I installed a new version okay from 44.4 I don't know what will the number some remember particular point some number 4.45 then is upgraded to 45 version that is no you're upgraded to another version for define we start testing in this but that is sanity distinct that means you're actually testing it with a no different version. That's what it says. Yeah, I mean, the new version is going on well with it. So now that Marlin is working well with the system or you know, whatever application Okay, so that is sanity district.

Okay. And then go to regression testing, regression testing, it means it Okay, so regression testing is once after you're done with QA, okay, manual restrict. Once you are done with the manual. You are Send me the manual, right? So you're doing a you know, manually of everything being by your click buttons and you know, you are manually clicking that and every application you are checking that manual regression. Normally it's not done in the minute.

So what happened in the regression? Everything is that include, I'm sorry, everything gets integrated with a no new new models come up, everything gets integrated. Now you don't want to do manual district. Why do you want to do double double work? Right? It's like, unnecessary work.

It's unnecessary. You did the same thing and no, and your boss says, do the same thing. Again, it's, it's not feasible. It's not like I'm wasting time you're wasting, wasting money and you're wasting resource. So that's what you're missing. So that's the reason they come up with a regression that means somebody else will be doing that.

Okay. You don't have to do that. Or you can do that same thing or but a different two you have now you have to use the two because they're not manual. Now you're using UDP. Okay, you are you're okay with this professional. unified functional testing no some tool to test there are Selenium.

Okay, to desktop application. Why do you need a tool? Because you already done manually? We don't know. We don't want to do that again. Okay.

So now every module has been integrated and there are so normally in the regression testing is testing the whole application has no code for any motivation. Another example of the check up some code can injecting code something okay. In some browsers and they all know some of the modules and they want to see it again. So that case your streak again regression Okay, there are some places who regression testing is also be done manually. Okay. I don't want to talk about that.

That might that is a different scenario. That's a different requirement. That's a different kind of a different but generally, generally regression testing is done by the to automation. Okay? And then you have like an acceptance testing acceptance testing what do you do? So, this is like you know as a high level as you okay you want to be specific then you say you add user acceptance testing that means it is done by then it all is all the testing is meets the requirements specified customer requirements then you know user acceptance testing as I told you like no there will be some USD t okay are you will be doing that no normally not we don't do that because you once you done that you don't want to do the same thing again okay you want to different projects that had been destroyed but you don't do the same thing again and again twice in price so that doesn't make sense.

So you always know we need a different skill set. Always a different skill set is required. Once you do manual you don't do you already you know somebody else will do if you're doing you already don't do manual. Okay? That's a different story that it might be schemed. Similar work, but different Requirements the way they work is different.

Okay? The process is different it's okay that all these things are different but it looks like similar okay manual manual, what does it mean? Does it make difference? No, no the way they are doing the different the requirements are different The procedure is different, the process is different everything will be done even though it looks like both are meant okay. So that is you ready? So that means it requires the customer to know all the testing is done by the differently.

Add, okay, then you have performance testing. So in the performance testing, do we have like to where they told you like no, no testing and stress testing? So, in Dota, no. So performance is normally non functional testing, y'all call it performance testing. Okay. So I already explained it, why do we know?

Why do we need performance testing? So in this performance testing, so we have, let's say no to we want to test the performance of an application. Okay, how the application is? No? Is it application is slow? Is it fast or no?

On how much time does it you know, it's getting so I've explained, you know, using that Amazon, lets you know, how much time will it take to log into if it is a new, okay, let me be specific on this if you are using the amazon.com. Now, in the end, it's not never logged in before it will take more time why everything will get installed the cookies and you know, whatever all those things cache cache memory, you know, everything will get updated. You get, you know, new caches, new cookies and all the stuff, but when I'm trying to normal, next time, it will be fast because I'm the cook And no caches are already there any stage no time. So that is what important Okay, so that you are taking or not taking time, how much time it is taking. Okay. So that is, that's all you do in the performance.

Okay. And I also told you like, you know, there is a load balancer where you actually balance the load. For example, let's say, you know, the users who are logging into system, you know, amazon.com. And, you know, and if the reaches more than beyond a specified limit of the server and server, let's say, let's take an example. Okay? can be more than that.

Let's, for simplification, I'll take like 50 users, no server handles on the computer now. And under a million people who are logging a million people like you could only do a server which handles 50 users, a million people then the server gets blown up. Application might be slow. Our server gets crashed no hardware failure, certainly because Because why? Because whenever someone is logging into that, it it Some resources, not some resources, the memory or the space, or, you know, the bandwidth, okay, the bandwidth in some resources, it takes some resources. And also it takes a processor, you know, the server processor should run that fast.

It can't have any more, it has some limits to do this work, right? Which is like, awesome, right? We only can handle some ammo, but more than that, we cannot have it. Okay, so we can only have a limited amount of temperature the same way? No, the same way with the second one, you know, 50 users then again, and then you have a load balancer, then it works load balancer does it you have two three servers or any number of servers now it balances the load between this server and that server. So you can use same URL.

Now, whatever the load more than 50 users now that is put into that next server. Okay. So let that load, load, stop. No, no more testing. Okay. So that's what the performance is.

Is actually it is used when it has to load testing and stress testing. So load testing, it's like, you know, check the behavior under the load for how does that say when you're putting so much load? Right? How does application performs? Know? How does the, you know?

Is it slow? Is the application slow? Or is it the application is very, you know, it's not as funny or get crashed, or whatever is it? So you're trying to test that, you know, under the law, okay, so you're putting some load that makes, you know, 50 users, or 100 users, you're putting some load to that. And then you're actually trying to see how the application is response. stress testing is something like, you know, putting like, beyond the specification.

So again, it's a server can handle 50 users. Okay, recommended is 45. Let's say So looking hundred rupees as recommended is 45. Now granted going beyond the 45 no 4647 What does that happen? Okay, so that's an example. Okay?

And, and how much queries is getting queries, right? Whenever you use an application, that means it will some database query, that means it fetches some data and puts that data and shows into your no good pay rate, that's when it happens. So you're accessing some data from database. So that is okay. So that is also query right? But it's just happening automatically.

Nobody's actually know going in and or writing SQL query and you know, select star from EMP, nobody's doing that. It's all happening automatically. The query actually gets generated by automatically and digital database and pulls out the data information in there and it shows you the webpage, okay, that's what it happens. And then, okay, so that's the kind of query for that for that to perform ninja take some processor, right, but it also takes some time. So that is just a stick for how much you're trying to scale that server is just another way of trying to send some applications almost the others application is point after putting that much offset, okay. Then we have usability test.

So you we do usability means you're actually trying to feed that user friendliness test. So hold on I know Java as a language you will learn afterward. Okay, so again Yeah, example of that signing button right? Whenever we go to amazon.com. Okay, now I want to see Let's sign off from this. This is a night he wants to do.

Okay, now let's go back to. Okay, so now when I'm trying to buy something, I want the signing button right here, right here. I don't want signing but I need some I know footer of the page and some insignificant place. No, I don't want Sign In button, right? They'll also see. And I'll be surprised, you'll also have the signing button here.

But the signing button should be there, right thing my friend and I refer to that is user friendly. So how do you want to buy something I want to log in. So it should be there in the right in front of my eyes. I don't want to research on just on fire sign in button to just to know sign into a webpage. So that is not enough. I'm just giving an example don't have to be that way.

Just an example. What is the user friendly, I hit Enter And I'd write I'm like, Why do I have to just, you know, go and do certain signing button just to buy something else on it. I don't like to sign up and buy from eBay. Okay? So that's how it is right now. So that is user friendliness.

How the application is user friendliness user friendliness people don't care owned by Okay, so that's what this is. This is the most important aspect right? So whenever this customer right, every everyone wants user friendly. Nobody wants harbor don't want user friendly. Personally, I add on these are free. I don't want to do some research to test to find out some, you know, I can't think just in a webpage.

Okay. There are website which is you know, which is not user friendly, but still need to know they are not top level. Okay? Just like that. Okay, good. That's what you need to know.

That's the use of elements. Basically, navigation is children. This is navigation. Okay, then you have installed and uninstalled is where you actually so we'll show you right and once you install a software it gets. So many things happen registry keys get updated, your dll file gets updated, everything happens so many things have you don't know like a lot of things get updated. Now you want to test once so let's say you have installed something let's take messenger your messenger your will say anything you say must have is for every anything which is installed in the system is any kind application model.

This is done with a client application not an web application. Okay? Because once you install it, now you are still hidden although share all the features are there and are getting are getting updated. So all Those things so that we do install and uninstall and see that isn't performing the proper is performing the required functionality for now, that is install and uninstall listing, then you have recovered as the ones you know, how does the system recovered from the crash? Once I know they have a crush, and how does it recurse Okay, that is called becoming testing as a hardware failure, or catastrophic or whatever, then you have security testing. I've given you example of security testing it.

System is how well the system protects an unauthorized an internet server like HTTP. Okay. HTTP hypertext transfer protocol audio again, no one thing is the protest image. HTTP is the hypertext transfer protocol secure. That means whenever you're trying to buy something whenever you're trying to do they secure so that's one way of testing security. Is it HTTPS or HTTP to HTTPS?

Not good? No, no See I never buy something we didn't HTTP I want everything whatever I want to say I never do my credit card information and images in which an HTTP GET IT, I don't even care or even if it comes from Amazon I don't care because I know that that is not getting you know that whatever my information is getting into third party and that will get into trouble and my integration will get screwed up, you know, so that's why it's gdps You know, that's one kind of security distinct. Okay, so and then you have compatible PTSD that will that is compatible with this or not, okay, so Okay, you're compatible. So how is compatible is the software compatible with the Windows is it compatible with the Mac is a compatible lineup for each computer compatible with the Unix almost six so that is compatibility Okay, the same browser which you install in your in the window doesn't work in the Mac, because Mac support doesn't support the eggsy files.

Okay, so you need a separate browser in order to get juster I'm sorry, it's separate I forgot the extension what is using the Mac? So manga and use the guardians effects it is different than a no you need to find out or either convert that He exists and all those things. So that is a compatible so is it compatible with this? Or is it compatible with that? So it's like you know, t testing there and then you have comparison testing. You are comparing that you know, weakness and, you know, strength and weakness.

Okay. So let's say you have two $3. And you are actually you know, trying to see that application, how it's performing with the Chrome browser and how it's performing with the Firefox. You're that's like comparison, you're comparing, okay, you're comparing with dis with that. I will do that to this comparison district. Then Unlike alpha testing, so this is like in a house environment where you actually know once your release the product, okay, I think it's still in development, you know, end of the development this year have developed and you know, you want to do the alpha testing, then you have like, you know, a huge in house that means, like, you know, the people who are actually working the back project like developers, testers be product owner Scrum Master anyone, okay?

They can be separate team, the don't have to be the same people. No, it doesn't have the same people separately do different things that are completely different skills, right? same same guy who is doing the same bubblegum they don't want because they know how to invert the cave up. So they don't want that guy, but they want a different skill set who has a different level of thinking who can do so that's why they might have different team to do that. Okay, so that's all for this trick. Then you have beta testing.

So this is normally done by Users end users like customers to overall you know support some software. They're around to some software and they want to test by the end users. So then you use beta testing okay. So, this is about testing quickly check on our Valley. So that was a theoretical view and just to understand I know answer any interview question but actually you will be working only in this kind of idns cases. So you will be viewing this application to the payments.

Logs on your application. Let's say you have an application here. Okay. And then you want to tell this Okay, then you want to see every all the parts of this application to see majors the static tags, okay, you will be having a requirement if you don't have any comment, then you have to use your Knowledge are your common sense, okay? You might not always be you know, everything will not be there ready made. rush me everything done in this world nothing has been ready made.

So there are no requirements you have to manage without requirements or we can no contact will be a scrum Scrum Master product owner or developer and then find out what is you know how these things work. Okay, then you let's say click on a button so we want to test everything, okay? So make sure everything is there. And then we also discussed about so now you want to order this stuff, okay, so I'm putting this last value because you need to test everything, everything should be tested. Okay, that sea water will go to what you are going to test. Nobody will tell you because that's your job.

You're supposed to know that so nobody will tell you Okay, you have to test with this. You have to do this on your experience. That's They hire you build on the experience right not by you know your skills they expect how much experience you output you can test okay and then you try to play guitar and then you start handing off he also find in defect is a shipping handling. There is no way there is no way you will have $5 of shipping when you're trying to order these many million dollar per upset okay. There is no way you USPS will ship you for just $5 I mean the company will give you for free that's a different story altogether but it is the it is not free. Now USPS is not doing any social service.

Okay, they're doing business right? They don't charge us one. So they buy a company with operations you're buying this product this much. You know they might offer okay we will not charge you shipping and you know handling fee. Okay, so you can buy this product So you want to testing? Okay, that's a very good question actually.

Okay, that's a good catch. Let me give an example of a neural testing that good. Okay. Normally I have not done any URL testing. Maybe look some part, but Okay, let's take an example. Here you are, no, let's say the URL for this.

Okay? you're clicking on this 3% don't think okay, right. So that now the URLs getting changed, right. Make sense? Now, backpacks, okay, so did you see that the page actually got shifted. So the bed you were supposed to be up is gone here.

Okay, now I'm putting a page here and you No agenda you're like put let's put okay so did you see that the page got changed so now this is like your testing when you're trying to put a new URL. Okay, the page is getting navigated to that or not because the whole page has shifted right and then let's check one more thing on all the pages here right? What do you see the page see the paid content? So this is new or interesting. I mean, this is an example i'm not saying they will reorder single example just to make more to make your like understand what is the order? Okay.

We are changing the URL but you're seeing the page is getting digital this can be a requirement. Okay. This can be a requirement see Jane Doe No, you want to attend to make sure that your page is navigated to the appropriate location, no matter that document on that and it will work on that. So again, so this is an example of you are alleging okay and then you place an order and then you fill out all the information here. Then you have that okay and then you put the phone number Registering and then I'll put the address you know, billing address begin billing and as the same then interchange the billing address if the bill for everybody knows what his billing address and shipping address, billing address in which your credit card is actually no, go to the actual key make sure whenever you're trying to look that should match.

See, okay these two things are different shipping address is different to billing address billing address where you registered your card and card or mail gets to that address. Okay? If you did not send in your bill, no, change it. Okay, you're going to do that testing, okay. It may vary, I mean, going more detail level. You don't have to be an detail level, but it's based on the requirements if there is a requirement on that.

Okay. Then you have to even also test that. Okay. Then you place the order. Then you get you know, this is your receipt. Okay, bill to this guy and ship to this guy.

Okay, and then you have for digital yesterday and we find so many bugs. Okay and of course there's a bug for C as always you need to be obedient to opinion is very important in testing coverage. So there is always an issue. So if so if you want to take an issue that's a diminisher if you know if you want to learn this to work, that's my thing is that because I need a job and I'm doing this and I don't care, what is that issue? I like that production page. So that's a different story if you don't want to, but if you are really seriously know working on you're like, Look, this is this is what I want to be.

I want to make things good then. Every software has an issue, okay. Every software has bugs. Okay. That might be a feature Okay, that then Okay, you don't like it just because you don't like it. It might not be a bug right?

Because you don't like it you know that cannot be issued just make sure you understand. Okay, I don't like this so it's an issue no. Okay. And then you know you need to find out the only thing is the only way to find out is this like this example you need to find out go to here and this is any No, Tara, I don't want server one server error, right? Why do you want to give a server error to this? Okay, so that is okay.

So we have tested all this, okay. And then we also I also like an explained rally, okay. So then here we have Okay, so I've shown you like, you know, I have not seen showing you how to create a user story. You guys have created that user story. Okay, good for you. You guys are good to go as a product owner.

Okay. I'm not sure about clear because my whole point of this training was to give you a QA but these guys are interested in going into No. Business Analyst. Oh, no good. So you guys can go as a business analyst askew and also QA because you can if you can open defects and you have good, you can open a user study then you're good as business analyst, right. So, okay, so I've told you how to create test cases.

So here we are in a new open task, okay. Some guys have open task, good unit open tap, whenever you know, because task is you know, you want to divide the work. There is a chunk amount of work and you need to divide into six parts. Let's say no six parts and then you know, Then that didn't agree the task okay and then you have then I told you like on how to open a test cases okay. So, you go here in the database module and go here and you know read a test and create a new test case and then you fill out all the information about the desk, what is it all about? And then you know put at work know what kind of test cases it acceptance of functional performance, okay.

And then you have which method or the method or menu and risk Okay, so how much risk that this case is high, medium low, I go with the medium, okay, although discuss or medium, but there can also be in high. We don't know, okay, then is it important? Is it useful, important or critical? Okay. And then I showed you how to open a step, I'm sorry, how to create a step. So that is a Test Case, and you need to open steps in that, right?

So I've shown you like, you know, validation input and valid expected results and always, you know, what is expected? And what is actual results always. Then I told you how to create a steps in your ego go here and, you know, so let's say for example, I want one. Okay, so then I get, you know, one test step to step in and I can create, you know, my test. And then let's say, you know, one is not enough, I need more, okay, let's create a tree. Now for tests, okay?

Now you will you see that, you know, these guys can doesn't belong to this test tech, or this test step doesn't belong to here. It has to be up or down. Okay? You can do it here, okay? So go here, go here and move the step up, step down, okay. So these are the functionalities into this rally, okay, don't have to be everything should be here.

I'm just seeing an example. Okay, and then you want to have a lot of preconditions, okay, what are the preconditions and postconditions? Okay. And then if you If required, you can also put the notion that okay, well, I wanted to know, is it is it passing? Or is it the test case you want to know, I don't know, default that test case or you know, you want to wait for developers to respond or wait for your managers and whatever the reason is, so can I teach you the rules? That's supposed to have a knowledge management, okay.

And then you have then I told you how to execute a test case. Okay, that was just creation. I told you like, you know, go Google is by icon we'll find another plan, you know, process. And right, tick mark, is that it has three functional design icons, right? This is copy, edit, and result. Okay.

This is the reason we care. You get a new test result. Okay, what is the bill you're working on? You put all the information here. And what date? Is it passed?

Is it favorite blog? Whatever. Okay. And then attachment if you want to put attachment and no, of course I would write note. Some people are getting very good, at least to be honest done. You're good in the class.

Okay? Don't have to be that way. Don't have been smothered. There's nothing like there is nothing like a hard and fast rule. All you have to do this day you might come up with better no better way of testing than me. We can get an outdated at one point, right?

So you might be no better than me. I'm just Sure. Really what I have learned, okay. So no, it's okay. Always I would like to put in notes and then update it. So this will get updated here.

And then so This is about execution. And then I fully open and defects, you know, go ahead and then defects. Make sure you're in the flow when you're opening defects. You don't go here and just have defects and our open dibs on board and when you do, you can do this, you can do that. But make sure all that user story is linked with that one. Okay.

Okay, so, then go here and you know, just go to the defense model and open a new defect, okay, and you open a new defect. Make sure the defect is in progress unless specified. Okay, release whatever the release you're working on. If it is blocked, then you know ticket block. And then iteration What did the audition and plan estimate how much time did the defendant get fixed? Almost time, it should be good things that I would think of that should be in a developer point of view.

How much time will it take to fix the defect? So it's very completely whole and sold based on the developer point of view. Okay, is it okay? Is it an architecture defect is a core defect or is your document defective? Whatever? No, whatever the reason, you know, so, invasion is how much time it is take it, then it's notes if you want to write notes, so so that's a defect.

Can you assign it? Of course you need to assign it to. Okay, you need to assign it that you submitted. submitted by the studio name, and owner is the owner. Yeah, owner owner will be the developer guy, although who knows Are the defects responsible person responsible who is responsible for that defect not tested to be a some developer guy or some other guy who is actually you know, because that third guy who has to fix that defect with a donor okay. So this is all about you know creating a test cases and then executing discussing our main defects then we go back to our old story.

Okay, then LDLC when we talk about LG, LG so they don't realize DLC the software development lifecycle which has no which are 10 phases, you know if you can remember that good intro, but I would not really go that that far. Because I cannot remember 10 phases. I don't want to remember after that, because you know, after that you don't even know you might be working on different models altogether. That might not be our modern so that doesn't even require Okay, so deterministic phases we as I said like requirements design implementation, test installation and maintenance when I talk about the waterfall okay similar to this and then what are the strengths of the waterfall and what are the weakness and then we talked about the V shaped sdlc model okay and then we have the extent under no disadvantages and then you We also helical linear incremental jlg we have talked about Indian agency.

Then we have like sdlc spiral DLC where the same thing you know goes round and round. Okay. The same phases, what do we use? Okay. Then we talked about the HIE Okay. So I di to where we actually know right then we discuss about the scrum this might not be good to see.

Okay. So then we you know we talked about various terminology who is product owner who is Scrum Master and he is developer and you know, Scrum meeting then you have like on a daily Scrum, then your sprint, okay. Okay product owner then we talk about burndown charts. Okay, scrum team and then we are actually in a sprint down on chat. We talked about Okay, release round on release burndown chart. And then we talked about backlog, what is the backlog and sprint and high level requirement?

Right? It's an high level, what is a user story? It's also a requirement, it's a little better requirement that is a high level that means no backlog No, somebody says backlog to get nothing specific, when you come to a specific then you sell us a story that means Okay, so this is the user story, this user story is assigned to this team. And this user story is working by this guy and that is a huge blow to this team. So it becomes very understandable because it is backlog. Okay, backlog what I have to do with that, so there's like that, so isn't higher, okay, maybe I will high level and then we also discuss about Okay, and the process how the process works in a no longer is printed like for 30 days.

Okay, so I stopped here. Okay, so any questions any question physicians are coming we are most completed all servers as per my no view, but nobody you know, told me anything new So okay, let's see if I have tomorrow alien I can discuss about this field, you can go ahead and read some of this software interview questions that will be helpful. Okay, and then you Okay, so you guys have to website to practice, okay? So you can go and practice. You can work on rally, okay and should be good okay okay. So, if everyone are good, we can close the class today.

Okay, good. Yeah. Thank you