Okay, good. Okay, so if you miss something, you know, you need a shot from scratch. Again go home design is tedious, but it will take too much time. So you found some issues in Camtasia. Right? You want to go to scratch.

Okay, so that's the reason right? What a fine is it all I mean that's the way they thought before okay. So there are some you know, advantages and disadvantages of the waterfall methodology. So waterfall right do they say okay you can say the same information that is water in like seven like six. Okay. What does a waterfall waterfall model is an iterative and incremental process.

And it contains the requirements design conditions and economic common design implementation testing, establishing mandates. Okay, so I've explained this in a CNC so you can you know, notice the same thing Now what are the advantages for it? No, it's very easy to understand Okay, that's fine. Okay, this is one good point provide structure to inexperience Shantanu will not explain that there are some enough time to do this because the waterfall right will have plenty of time to do not like HR HR is very fast paced and needed to run and like nothing it's like you found that today issue down into our it's fixed now Go Go check that it tested it makes take on production that's fast you know they're they're trying to move fast to move and then waterfall it takes like longer than six months one by two things which are done in six months in a start in just one month.

That's a finish. Okay, so that's why you know that so advantage like you know, provides a shot check in individual will have enough time to understand what's going on. Okay, see the documentation conditions are what they are supposed to do dishes You know, this is a procedure you have to follow either the policies, tailor the regulations and so on. They have enough time to do that. Everything can be done but you know, there's no time. But in order for you have enough time, and this is like, you know, requirements stability, see this is motion, but why is the requirement with stability because in waterfall once requirements are done, then it's done no change if you want to change it from scratch, again, there's no going back, right?

So let's say let's take an example new project or project for lightning waterfall. It's a six month project. I'll move on some issue in the third month even working on do you cannot do anything so nothing to do third, man. Okay. I have to wait for three more months and then go back. So this will not make me to take it literally.

I mean, I'm trying to explain no how. How you think this is no more? No more? Yeah, they might be following the same thing. But it's not that effective. Okay.

It's not very efficient and effective so that's why not so that's the reason the recording stability in once the requirements are done they're done they'll keep changing but in general the key key today never want to come in tomorrow again the same becoming gets into like one not even one day the woman got change morning told me that there is no stability in Asia. But here you are recommend stability for management control Okay, this is good for you know, because you have plenty of time to do what okay you're trying to plan stop tracking everything, everything is pretty good. works there. This is very important. See, I like to see this No, I like to work with quality is more important than cost or if you want to maintain quality as a QA tester, not merely some QA engineer and all those things, right? You want to maintain while you're your hire where you have to make an apology, there is no quality is the point.

You find right? So then the reason Right, that's why I like waterfall. You know, I like waterfall mode because you have enough time to do everything and you are you are actually worrying about the quality not about the cost okay price not each other who cares the management is paying money, I don't care. I want quality right? So that's the reason you know what fun is good at colonies to say you know, remember this point. So this is good for waterfall.

You're working in your company quality is more important than cost. And then you have weakness of waterfall that is all the requirement must be known. Okay, all the requirement of course, if you don't know something, you cannot go back right. You need to know everything on the end. Before exam, and deliverables. Okay, yeah, this is flexibility.

Okay, so the third how much flexible and living off agility for customers so the reason right so let's say customer is demanding like no voltage three months we'll say no what are the customer three? Why no I want it in three months and I have to wait for three more months. So that is the problem no linear opportunity for customers customers no it will be too late. Okay. So that's our weakest that's why they are committed Okay. Um although when do you want to use the waterfront on when you when you know the requirements are well known for you know be part of the requirement is good and everything is good you be using requirements product definition is stable and you know what is it no productive good work your product instance make whatever you're trying to deliver Okay, that software product stable and it's no unstable.

Okay. It's suddenly if it's too late we'll be mad at tomorrow didn't blow up the webpage right? It should not be a veteran. That's right. There you can use that one. Technology under sir.

Okay, new version open. These are the next few other points to use in waterfall. Okay, this is the web and you want to use and then we have the shared sdlc. So very low told you already read we have the same things again requirements Okay, so I'm pretty sure okay. So this says the same thing okay requirement running and requirement analysis and architecture will detail data and query unity. So these are recommended arrows show that when they are being added parallely these two things are being done, no maintenance they are being at the same time they are requirements and then again you have nothing else and acceptance testing is being done.

Okay and you're doing B And here they are doing integration. So, this is like you know V shaped, which represents a model that means the same things which are doing here like they are doing mission match. Okay, the same things. All these things are like, you know, whatever we have in sdlc they are doing the same thing, but the same parallely they are doing well, let's see. So, that is called V shape because it's kind of V shape right. Interesting.

So, personally, I have not seen like no V shaped agency model. I don't know how convoluted it can be. But, you know, but he of course, like you know, in companies, sometimes they have their own methodology. No, they are my people me doing everything like that. Okay, so some people have their own way of methodology. They have their own you know, client perspective.

They have their own standards of doing work they don't depend on anyone okay that's also possible and then you have dessert as being points on the ship okay. So, this is one of the advantages for the ship. So, this is like you know the whenever you want to do verification and validation of a product then you know you will be using V shaped V shaped progress DMC and each deliverable must be testable product management can track the progress easy to do okay. Then you have the weakness for this does not easily handle concurrent events, okay, whenever you have two concurrent events, right, it cannot, you know, use this vision does not handle iterations or phases. Okay. Yeah, that's a good point.

That means that like we want to do iteration iteration to like two three things to be done the same thing. The different values say that I didn't know. Thank you. With the different volumes, you want to see the beginning, you cannot do that you cannot do those two things at the same time and the same level, right? So you need to make sure so that means somebody spins up there now, we don't want to hire some one more team just to do an iteration, right? That's the reason it is not good.

Okay four iterations and dynamic changes in recommender dynamic jennasmith everyday requirements changing they will normally form and the same thing is change tomorrow, okay. So, that is not good. If you are using V shaped with a V shaped mark, and then does not content risk analysis and that's fine right. Everything now everything is a risk risk analysis is like that is managing risk is a composite. It will be there anyhow. Want to believe it or not?

No, that is, that should be no, that's no no point of using this because you can't any risk analysis. No, you will be having a risk right. So what kind of risk? Okay, oh, there's so many things okay. What we are Testing so we are testing Okay, functional testing we are testing regression testing we are testing accommodating load testing stress testing. Now we know we don't have time to do all the testing Okay, functional testing done after that, okay, we can do for one to four regression.

So who is going to handle this performance obligation so the page is not responding properly but pretty stuck because we got too much of server and so those are risk so those are example something that example okay? So don't take it as granted could actually risk terrorism and that's one of the risks that you're not doing something okay? So that's the reason why you cannot do this with a V chip. Okay. So that's a weakness. So you have like when you use a V shaped motor, if you know all the requirements are known, then you use a V shaped model Okay, and can be modified to entertaining the requirement.

We are analysis face Okay, and you know, solute solution and technology, you know, these are like outdated. Okay, so the nutshell like, you know, we'll be using V shaped model. But yeah, it's good to know, if you want to, like, you know, need to get a project of V shaped, we'll be having some ideas in that. This will be like that. Okay? And this is the model.

Let's go through and read this. Okay? I'm just explaining other at all This is one more in one hour gone into structured, evolutionary prototyping, you know, you can just look for one type of methodology. It's not exactly symmetrical. But you know, it's kind of one of the process like, you know how you're going to do. So, just one more right now, an application model, you can go through this this is not that important, but at least we can just go through this document and now you have to implement the sdlc model Okay.

So now you will have that means that you're done with dishonored sdlc and waterfall and the V shape. Okay. So next now, this is incremental sdlc process. So it is incremental as they try to re implement the name exception rates increasing, always increasing. So you what you have is like, no, you're doing Same thing again, design code integration implementation operation. So here what you're doing is here your verification okay unit testing product verification system address revalidation here you're increasing again to verification no here you're doing validation here what is there this system stability software transfer comment from the central everything about Only thing is we are actually implementing it implementing do no verification and validation.

Okay, three of this that's why we call implemented sdlc model okay. So this is huge when you're when you have like major functionals Okay, when you when you want to do major functions first time you know later when you want to go you know other which is optional, okay. So, this is important as weakness, you know, it requires good planning and Okay, so finding this total costs complete is not lower. So nobody wants to prefer that wants to do that, because you're fated. If you have more weakness, and then less strength, then no, no, no company would prefer to go with this. This will unless you have some specific notes from your small team and they want to do this.

The reason is because not too many, not too many chocolates coming off. So otherwise, right? In that case, you know, you'll be using a small team. No, that's okay. Funding is based on our team. So that's, I mean, that is, if that is the case, right?

We can use But otherwise, no one wants to use that because it's nobody wants to waste money, right? Everyone wants to be quick. And you know, they want to do the job done in just you know, in months, right. Now, one month is finished. Everyone wants to do that. So that's why This is not much preferred Next we have a spiral sdlc okay okay the same thing no plan no plan requirements design implement okay for develop okay.

So, but in this case right you start from determine object use again you go here evaluate alternative identify risk and then you put the prototype then you come to the concept there you have requirement to design implement and so on again coupon, keep on moving, it's finally that means you will be until the product is delivered you will be key keep on doing this and around and around. So, that's why you know, that's why this is called like spiral methodology of four quadrants, right in the four quadrants you have four different levels of no pages for different level pages and lead pages you have likely in this phase you have each time of Allegro that display cannot develop in your favor. You will have the common design agreement okay. blank page, you know, you will be, you'll be having various pages in approach level. So you are you are, you know, when spirally the same things same sdlc process, planning, design, loping returns all the things you wish during EFC.

But here, the way that the way the work is done is different. Instead of waterfall, the waterfall is like you know, from this waterfall from top to down, but here you're actually going round and round. Okay, so that's the same thing, the same process. So this is a process right isn't the way the way the way the work is done. Okay, so there's a process for this is this process is more for a management point of view because they want to see like, what should be done and so not very important for distressed testers, developers, everyone will be doing the same thing creating test cases. thing that the same thing they will be doing this for them, it doesn't matter.

But we need to know these are things the worst will be one either and when people are also right okay. So then this Yeah. So, this is what are the current contents in the spiral quadrant in the first contract it conducts this for a document object your alternative constraints and what are the objectives the functionality performance critical issues, alternative build reuse okay constraints costs sheduled interface etc and then you have another project. So, these are all the quadrants quadrants information. So, now, the third quadrant like you know, besides creating didn't review the report, next you have like four quadrants. So, this is like you know, explaining each in recorded so, what we are trying to do, okay, then, you know, the project plan and all the confusion on how Is the test plan material so you're doing the same thing, but the way they're the way the work is being done is different Okay.

So now you have like strengths and then you have Professor indicates without much cost okay humiliating processes because literally there are like you know strength for this final amount and then you also have no this disadvantages this model is complex, I know personally I feel that discomfort to remodel is complex, why we got like four quadrants right four quadrants now if I want to do for create test plan test data down which quadrant I prefer and when I have to do to this is a complex Right. I mean, personally I feel that is a complex. Okay, it might when you get into profit magnet simple partner, that's when it gets low when you get too many issues right? You have too many issues. work, right now you're nowhere to wait for content that you know after designing after which the complex reason, right. So I prefer using complex and you know, not very effective in today's today's technology gets outdated, everything gets outdated one to one point of time.

So this is a more outdated like for medium and high risk pilot this you can use and the US are unsure of the knee. So this is a very good data when users don't know what they want for that problem, right. So when they don't know what they want, and you say like okay, which, which already, they don't know what they want, and they know you want to do in complex favors. Nobody knows whenever they want to tell me whatever we do it in that quadrant. And that's it. That's it.

Okay. So, and also, like, requirements are complex when the comments are complex in sense, like they don't know what to do, okay? But I mean, we made a requirement and you know, they change it. Now we want to think about it, we don't want to worry about it and when we shipped it requirements are complex, they keep on changing. Okay? And they are liking the changes so that, you know, that's the reason we are to use final model when these things are, okay.

This these are the things which are if the user want all these things, then you know, you can use polymer but I mean, it's still like it's not very effective. Okay, sorry. Don't be explaining that. Okay. The demo tomorrow, the explain So, you have one more like you know Extreme Programming. So that is adaptability there are so many okay but on our liking nobody uses that okay.

So, this okay. So this is so we are done with sdlc sdlc and various methodologies. JOHN McCullough Julian said that I will take complete class for tomorrow because I want to be like no more, be more detail on a day so that everyone can now understand So any questions in this sdlc and other methodologies waterfall and spiral and there is no emergency and we should be using any questions so in respect of your one nine This is more for him this area so somebody asked the question how important at what point of view that's a really good question okay. So this is more for no you can just understand this for as a interview point us in front of a interview you can understand this one But at work it might be completely different you might not even know all this nature of sdlc you know you have to know it and nobody will tell you that because as an experienced candidate you know, nobody said until okay we are using this methodology to get some really friendly people and we need to help you out to the table otherwise, I don't think you know anyone and nobody will tell you like which methodology so you need to find out yourself okay.

But this is more for a I'm actually explaining more for interview point of view rather than one from one point of view is completely different decision theoretical. So, you will not be doing anything related with this, you know, going to our trading desk or reading discusses or executing that you know, opening defects all these things like a management perspective in what the process they are following the barriers What is different Okay, so so let me explain this. So there is one more like done with sdlc kobu sdlc Okay. Okay so let's see if we think we will get A chance to do revision. So since we have one day tomorrow at any age and finishing this, so hopefully, we get a revision and enough, have some interview questions. Let's see.

How does it look? So hopefully we'll be getting that. So the first Monday and Tuesday I'll be explaining that one, UDP and loadrunner introduction session. Okay, so sdlc luckiness. We have studied about hdc at software development lifecycle, and this is sdlc software testing. So there is a difference.

All the ways can make up the difference it is DLC more for it, you know, management perspective, I don't want to sell the local perspective. Okay. It can also be like no development and sdlc more correct. In our testing perspective, okay. is good Like, you know, so we everyone knows about it like developer or tester manager or Scrum masters director, you know, CFO is CIO and all the people who will be no CIO and the people will be moving more for a management perspective there will be knowing all this data, which we already have to choose which is good and which isn't, which is going to be worse, which what will be done faster, which will will be cost effective, all that stuff. Okay, so there will be doing better than that.

So the sdlc is more for a management perspective. sdlc is more friendly for testers. So now everyone don't No, no, no, I mean, everyone doesn't know about sdlc sdlc will be involved during QA, QA testers, okay. QA lead, okay. QA manager, your director, anyone who is QA related to do it, okay. You want to have some The company has a QA, QA, CFO, QA, cio then they might have a big big company they might also be doing.

So that is like so testing lifecycle, so this is only done by the QA, okay? When you ask go and ask what is sdlc developer? Okay, learn to try that. Okay. So, in the early, no, this should be normally to the QA, okay? But what you do in this testing lifecycle, so this already here winner completed, okay, test plan reputation test design, test execution and test lock progression.

Okay, defect tracking, test report progression. So report progression I already told you, right, so we go to that again. Okay, so the best plan so test plan So you know this test is a high level document which contains all the all the different features and all the different models you can have different models regular foods to be tested what is the truth and it's not integrated etc do not okay there is some partner to strategy documents alongside one more started to design okay not required but going on something on their own so then next you have like digital design okay once you're done with the test plan, you will be creating test cases right okay, so do you notice cases like this in a high level document? Okay test plan is ultra high level document which is which is which is created by the please pick me okay test case design test cases done by me Okay, so let's get this out on a high level document which is done by the clustering pianist okay and the descriptor okay.

So, that is diskette is a new high next distribution. So, you will execute the test cases that is test execution and then you have a test lock okay fallen pass and fail information will be stored in this law. So, I have not shown you like no way that edge proxy this can be anything like this logs are like log points very low what is law normally, law fights in Unix normally you've seen a Unix so whenever you run something are coming from you will be getting the love file for that's not exotic desktop that's a log. Okay, that's all the information about the folder contains all the information about where the job is run when you executed deleted all of what it says done where the query has been the data where is it Have you know extracted the data where it has you know, entered the data as all those information would be considered law that is not actually this login will be any information that is in a Canadian passport information okay that is stored in the cache locked Okay.

Next you have defect tracking in all the free items will come under the defect tracking. So, you know defect tracking. So, you know you will be using test management tools in this case we are we are trying to use van mechanics always remember it the product you're working on, always the word just make sure because you're working on the picture. You don't want to work someone else project and if you do that no it will be when we get so many questions from your management program. So different I hear you will be tracking the defect. So suppose if the lead right, so here is a track, see, you can use the same thing, which is the team status and see, if I'm lead side doing all this information from these do watch how this information will be there.

So then defect tracking who has open defects? Not exactly difficult deviations a task, okay. defect tracking is where you're not tracking the defects. You can take an additional problem you're trying trying to try to fix it. Okay. So that is the history book.

Test reports is working well. So those reports which are generated right so just go to the report section go here. So these are our lead our QA right here we'll be doing this for now there are so many other reports so I don't know all the reports may not be updated as soon because we have not done everything here. Okay, but the reports which will be updated will be this one. Let's see, check the defect. So once you know let's say your boss has asked to send a report on defects.

So now, okay. Now you see here the thing. This is the report. Okay. So here I see like in a submitted status, so now once this gets to the boss, not your boss, now Bosman, you know, via your browser and see why are up there submitted status. When I told everyone to put in open status open at 25 good, who is the one who has put to the submitted Ganga causally?

Just call the lead manager Hey, can you check who is no no, there is no submitted two of the defects are submitted but not in essence Can you call that guy now suddenly that lien will say hey manager is calling to stop right? Now we'll get a bigger picture on that okay. So this is the thing okay. So these are reports so these are fixed Okay, which are green color that is fixed which is open which is a red color which are submitted that isn't open. Okay. So this is how you can generate the reports and then you can export a JPEG or PDF word in it.

Okay. Sorry. No, you get another print and you can Could they submit to the promoter so that is a test report so obviously whatever you're trying to do is that everyone knows that in the company that make sure you understand that. So, once you do is small and mistake right it goes directly to the manager for a boss will take everything perfect so even is like you know to start with but you know once you get experience you know outliner you will get better well versed know the way you talk and all those things but to start with to be very careful in everything because you don't know we normally what and what we're doing for that thing you know you have to be very careful in your team or people in loyalty, but then you have so these are like same mechanism test object you so Okay, so this is the test plan preparation.

So we are you already seen the documentary, so You know this I don't need to explain on this test it's designed with a killer document itself what are the various modules is a document test setting and resources for you. So this is mechanism you have like task duration resource and know how much you're actually contributing that amount of time to hold such as much okay so there is like dish manager so that that will be a bus manager is a scrum master is different, okay? Don't make Scrum Master, the project manager will be will be working closely to go find defects to crawl tickets to resolve the defects on not escalating those issues. Sometimes developers will respond and then you know, the prime minister will know cc everyone including your boss. And then again of course developer bashing and saying that switching up his face and release date is tomorrow and what are we supposed to do with that?

No no somebody will respond to that 2030 people okay. So, does this commercial to you all these things should be get escalated and all those things should be done by the scrum master. normally don't have to be that way. But here in Agile that will that is going to happen actually because managers are not taking any responsibility of stating the issues. Okay. And then you have a test lead, how the preparing test plan review this case and all the stuff and then you have a test engineer Okay, down one more guy you know, you'll be doing it, reporting, design and daily reports.

Then, test environments to you later. environment is dependent on three three ways in runners that is test environment production and development and production. Okay, if you have a mobile app performance, okay, but three major then you have automated tests Okay. And then you have like a scale design. So what does it contain together? Cygnet test case ID description diskette procedure.

So this is no all this is a part in a test case so how tricky is keeping this because while you're listening and then this long defect tracking isn't where you track the defects where we'll be having like, this is like going more into detail but this is all not required only sdlc see the only extensive 345 is going to be done. You're going to be detailed in that so that's what we are trying to explain it Want more detail? On every restaurant? Okay, did I ever really need what is contained for all these things you're doing? No, because as the reason you have 10 for 18 slides, but one page we have done sdlc. It has like five pages, five pages, what are the takeaways is plant escape design, test execution, test preparation, defect training, test preparation, but once again, you want to be more vigilant in how we prepare the scan very prepared before you can go ahead and explain this.

So that's what we're all about. Okay. defect tracking, you have to and then you have defect status. So we have defect status, I'll be explaining this, you know, we also have bug life cycle or defect right. So whenever you open a diversity, the new state that is not submitted, and then you have like open when you open and see the defect is open and you know, everybody knows that and fixed figures, ones that the robot actually fix it and writes it Mentally what was the issue the core issue architecture issue document issue or something else? At least my right information they might not be they will forget relatively speaking test you need to retest it.

Okay if you did if you once you retest it you find an issue reopen it. Okay now you argue with the developer saying Oh, it's not working the developer says it's working fine on my machine. So then you escalate the issue no talk to Mr. Master saying that hey, now let's talk for them and like we did good or not you need to close the defect. Oh, no, no, it's fine. Your brain get off it. And if it is no, then you know reopen the defect and you know, the developer will be working on it.

And it is rejected. If it is rejected. The reason is no, this is no more we are working on this and this is an outdated issue. Please check with your lead and work on the correct to correct one will not a different version, you're using a different project. This is not for the As an example right so that's how defect can get rejected. And then you have like you know we know security defects security, critical major and minor, minor a some minor issues like you know, example is like some static text on some font issue font.

Here another font who wants to indicate to the contrary, so, okay there might be no that is a minor, major major is something and what I've shown you like the shipping and handling fee will be shown when people are buying online and they're like touting it to famous amazon.com website. Like million dollar last item close $2 million. He was buying and shipping is only 500 for a very good reason already losing so much money so that is a major issue. Okay, that will be a critical point because we might, but to the same person. I don't severity you know point of view and then critically something which is a production issue, normally production issues but critical regions can also be SD okay which are required higher dimensional that defects Davidic critical okay. So, they have explained this one go through then your priority, so, so, you have this okay.

So, be on hybridity, moderate low clarity, see the similarities we are done with getting it right. So, the security is Like, you know, the impact of impact available, you know, what is the impact of Bob? what is causing the system to fail? Okay, well, so that is you get it, okay. The three are gonna disappear three days. Okay, we know remotely the impact of the book, what is priority priority is like, you know, what is the importance?

Like how much attention should you give to that particular defect? Okay. And it should be fixed, how much attention should be fixed? I'm sorry, how much attention you should give to that defect to get it fixed. Right. So it's like it describes the importance and order in which the budget Okay, so that it is more for a developer point of view to think that you want developer to fix right now.

Right now right now, they're included in most important so the worker will work only on your issue. Okay. So these are more of a production issue and hybrid issues which are stopping work. Work is really stopped because of that whole company robotics stop then you know, performed by a time developer will get lots of defects till you don't open it because somebody already opened so many times. So, okay, so that is the priority. Okay, so there's a difference between severity and priority.

Okay? Okay, clarity like high, moderate or low. Okay, there's three. But there can be any number of okay can put low leash. This has bootsy chick here. Studies show see on the series see here the priority see we will move things are here together take priority resolved immediately high tension normal low for normally things is normal or non higher tension is something which is you know, which is something you want to know more important for that lives all Java developer and start working on your issue so that you don't want to Mr. Director these two things are very important to make sure if you're putting this one to start with no it's not good.

Because when a developer will come to you Hey, what's up with you man? Why did you put Why did you put high attention is not even a defect you know this is done by the this is outdated and there's nobody in working on it. So you need to see that too. So this can you need to coordinate with your lover? I'm sorry, Italy Okay, say hey, this is a defect so what know what's the practice? I think it is a normal because you know, it's a normal issue and you know, it can be so that's integrity, okay.

If it is a font issue or in some static text, cosmetic, minor problem is something I do know something. I know some text, okay. major problem is making okay? problem you can also not exactly cosmetic, but you can also use the same thing of text is missing or no text. The information in the text is wrong. Okay?

That can be a minor major problem is something which is making all the spam open like shipping and handling, that's a major crash or data loss or something with the URL itself is not working. So that's a crash. Okay. That is a severity right? Hey, I'm nervous. GM online is not working.

This completely done to this will be high. Okay, so that is TMC. Okay, let's go back like any questions before that in sdlc? Any questions on anything that I missed? So you can go, you can go ahead and practice rally, not just practice, to understand the process not to understand the tool, this make sure you see what i'm saying you try to understand and I hope you guys understand that it, practice the process, not the tool to because in the you know, in real time, you might not go and use rally, rally, rally and non project you get from, you know, from I even I don't know, some JPA tool and say that, hey, mano de de taught me how to use this tool. So that's the reason I'm saying because everything will be different.

Practice the process. So what is the process creating test cases? Okay, creating and so how do you create Okay, go here, user stories, okay, here, you know, create your databases. How do you open different CNN echo here and open it affects how you make the report. So here you go into. So that is a process.

Okay? Don't get used of the tool. No, don't even get used to the tool because you might be using tool if you're using tools we're good, we are known better than your boss and you know you can do it and you can suggest your boss a pretty good experience in this tuner anyway, but that is not the case, right? That's not always possible. So, always know that is the process. How do you create test cases?

What are the test cases? What scenarios you can come up with what are the various scenarios Okay, price to pay to bond regarding any more Canadian there are plenty of 10s of scenarios you can come up with. So many scenarios, but okay. So that's no you can use that. Can this go back to Popular cycle. Okay, so in bug life cycle, so explain already right to when you have when you open a bug, bug or defect.

So it will be new or no in reality or in a submitted, make sure it is not a new should not be new unless the project is you're waiting for someone or you don't know it is a defect on all those things. Okay? If it is a new, like, put it as open, and then when you open it at that time you actually assign it up before that you assign it to a developer. Okay, so when you find when you assign it to the developer there, you know developer said no, no, no, get rejected. It's not a defect. Okay?

It's showing up good in my machine and gets rejected. Or I can do it another way like before default instance. And now they say no, no, we don't have time to fix this issue. This issue is very big, you know, I don't have time to exist You know, this will be gone into the next release. They okay they have some communication between the lead their managers their process or whatever. Okay?

They will have their own reasons and their orders things and they say no, this will be deferred. We don't have time to fix this issue, but there is a reason it will go on but before once you assign now the defects, if you're lucky enough to get that defect and it gets fixed, then you do test it. So now you say no, no, no, it's not working. No, I said this is the defect is not working and you reopen it, reopen it, okay. Now, when you say no, no, this is not my issue. Okay.

So stop by your desk and say, Hey, this is not my issue is, you know, assign it to some character. Oh, this is architecture issue, talk to your talk to architecture guy and assign it to proper concern for us and not mean I'm not responsible for this. So it's okay. Okay. Then, you know, he does Through that architecture and say okay well this is a document issue then you go to reopen the division. So, in this case I need to be that are some years from monster or some other person and I find it and then again we go ahead again district and the concept fixed already verified and then it is closed.

Okay, so this is the defect lifecycle bug life cycle. Okay, so we have three, we know normally sdlc sdlc software development life cycle sdlc Software Testing lifecycle bubble exit to finish his work, no bug life cycle is okay so any questions in Any questions for CFC? sdlc, or quadratic? Here are our most completed two, they're not that effective no more for a theoretical view. So this understand that you don't have to mug up everything, understand it, and answer it in your own way. You don't have to be your some specific it's like not a no Newton's laws and you have to be defined the same way what it is, but just try to understand it, what we're trying to do and what is in the know what originated, what you're trying to achieve with them.

That's not know just to be understandable. That's more important than mugging up okay, that don't help and then Completed implementations I died tomorrow I'm extending a day so we'll be done with the most of the most of these syllabus, then you'll have Monday we'll be having UTP and Tuesday we'll do the introduction just an introduction let you know how the automation tool works. So you guys can still practice is opening Eclipse so inviter open with the next good Okay, what I will be also giving you for free maybe today they are beginning homework since we are done with the most of them putting up having two days to do that. Okay, so it's already one so we have any questions, any comments, any suggestions? So maybe this was a good job Nice job defects were open. Good.

Okay, so display 21 degrees so make sure yeah, okay, so make sure you know, the more because you open it's not good. It's not always good to open your defect. So what I'm trying to explain here like you know, you want to be good at something you need to be either good at technical point of view or good communication point of view. Okay? So if you're not good at communication, so you don't know no one knows when you're introvert guy, you know, we need to be very good and technical so that they cannot do not achieve anything. They cannot move you because you are doing good work than any other.

We are good in confusion, okay. You don't even require that. You know, you Manager is something that okay longest manager and will become like a manager and now you guys use your developer. Okay, so any question so we are good so Can he can I close this class for today? Yeah, homework I'll be giving you all today. Okay, so you're having two days.

So that will be due on Monday at poker we'll be giving you today too. So whoever didn't get a proper chance to do that, say I feel that some defects are missed, right? critical defects are missed. So you have one more chance we're done then good is good to go non-dairy. They have a good challenge to do that. Okay.

So let's make sure that We're going to start doing good right this plan is pretty vague because you will be getting the same singer likeness plan okay in the meantime you will be having, you know so many other features and not features and all those things, okay? So you need to figure it out yourself that they call your lead, okay your lead database because you're managing tester somebody right? matter managers teams or potential lead managers for people right treat for people who are working under you when you need to know who you don't know that you know, you can have a meeting meeting with them and say what we need to create and what we need to do. So I have cm already sent me one struction site CPL suffer from not fear he's been calling me okay so this is when I told you right in the update the information 4.1 4.2 4.9 this is what I'm doing okay also updating the regression.

So in point one okay this is my this assumption might not be very clear. So in that case you are to call me know and or you can email me we talk to each other. Okay, this might not be very clear because nobody understood what it was. But no, you can call me and you can get the information. Okay. Okay, Any more questions?

Okay. Thank you.