Introduction to Software Testing Life cycle

Rahul Shetty
A free video tutorial from Rahul Shetty
Teacher/Founder of (Testing School)
4.5 instructor rating • 14 courses • 235,585 students

Learn more from the full course

Master Software Testing+Jira+Agile on Live App-Be a TeamLead

2020 BEST job oriented Software Manual Testing course on real time Project+Interview ques+Resume Prep+ Lifetime Support

10:19:33 of on-demand video • Updated May 2020

  • Crystal clear understanding on how Software Projects are handled in real time with Live examples
  • In Depth understanding of current Software Testing methodologies with Manual testing tools followed in the Industry
  • Understand JIRA and Bugzilla tools from Scratch with Live project demonstration
  • Thorough knowledge on latest Practices like Agile scrum, SDLC, Testdriven, Behaviour driven approaches
  • Strong exposure on designing test cases and defect life cycle process
  • Complete knowledge on QA process starting from requirement gathering to Project delivery
  • Testing types and their real time usages in Projects at different stages
  • Basic knowledge of SQL
English [Auto] Welcome back guys. So in this section let us look into software testing lifecycle. So first off all you need to understand that testing is not only limited just to find bugs. Many people optimism shown that walk cure. Thus there will just test an application for errors. That's it right. What's the special in that cure all. But that is not true. Cure have equaled role as development analyst or any other position. Cuba also plays a major and equal role in software development. People need to understand this clients really care about QE. If this is a simple job that everyone can go and test an application. If that is not really matters then vivo testing does still exist in the market. So for example let's say you have developed a billion dollar product. Okay so will your do risk by asking developers to do testing when you have a product with a billion dollars. What if that goes wrong. All of our money will go into win. Okay. So similarly people may tell you that testing will go away but it won't go. Okay. So if you have at least one million dollar and if you are trying to implement one project you will never let that project go without proper testing. From good perspective. Okay. It's just that people do their work but do not believe on that. And you also need to know that it's just not limited to find bugs. So let me explain to the lifecycle of that Tester when they are in the project and how do they perform activities on any data project. In the last section we have seen how a tester works in one specific sprint in the agile scrum environment. Now in general what does it Tester and Cuba have responsibilities in the project in general not specific to one sprint. Are not specific to one iteration overall starting from the project and finishing up the project. What are tester does and how he plays a key role in that. All that options will be looking as part of this section and because the whole life's taking apart tester undergoes as part of this project as software testing lifecycle. All right. So these are the different tasks you will be performed as part of you a job starting from requirement analysis until testing. Now I will go through each and every phase of this lifecycle and explains why does a tester do in that particular phase for their project. Okay. Now the reason why I have written this point that it's not limited to find books that Tester will involve in every phase of software development. Not just testing and application. Okay. So now let's get deep dive into each and every face and try to understand what are our roles in each and every face. And how would we need to solve all the challenges whatever we face in all these stages. Okay. First requirement analysis. The Q A TEAM THAT MEANS testers will interact with various stakeholders like client a business analyst product on a okay to understand the requirements first in detail. So let us say that there is one project which you need to develop the client have approached you are a team and given some requirements that he need to build as part of his software. Let me take you to one website roles will shift. The academy dot com slash and the practice. OK let's assume that me. Russell here is the client I have approached one team asking to develop this application for me. Okay so basically this application is all about filling the form and click on submit. So you need to enter their name email password gender and data but so that their user details will be stored in my database and then they can shop the products you can click on this shop tab and you can actually select the items which you want to buy so that when you select here the items will be added to that task. You can see that check out three items but just basic e-commerce app. So once you have selected items which you need to buy and then you will go to check out page and then the checkout page you will see that are the details like what are the different products present here and then if you want to increase that quantity then price also will increase and then you will see the total of all the products and then you can check out so that they will be taken to this page and you need to give. Which country you want this product to get delivered. If you give India then that option will populate from this dropdown and you need to read the terms and conditions go in parts of a simple e-commerce application. So this is what I need to be. So when I approach development team. So basically I won't have all these pages right. All this will be prepared once the project is delivered. So client will talk to you verbally or he will draw some diagrams build some prototypes to show how his application should get developed. Okay maybe once again right. So you need to interact with either lane if you want to directly talk with them or you can talk and interact with you are a product owner or business analyst sit with them first to understand the requirements to develop the project. Most people will be an assumption that only developers will sit in that meeting to understand what to develop. But that is wrong. Desktops also should go to that meeting and try out to understand all the requirements. Okay. So that he also should know how that product should be. So that he can test in that perspective. When the bill is ready for testing. Okay. If he if he or she is not attending this meeting they should just depend upon what developers say about the application. Okay. So you need to attend this meeting to understand it from client perspective or product or another perspective and then have your own planning or design off your test guesses for testing that specific product. So basically if you are a normal software engineer the best things in it and you are team you may not be called to this meeting in general. Q A LEAD QM manager will address this meeting not all the Q who are present in the team. So this should be at least some senior management in the queue who will actually attend this meeting and gather all the requirements. So this is phase one and this happens to every project. Maybe you are not aware because you are an Junior out mid-level in your company but talk to your managers and they will definitely tell you that this meeting should happen before any project kick started. So I would guess as in that I am like claim and I am asking to develop this whole application for me building this products and everything. Okay. So from that meeting you have to get these requirements first business requirements. You have to know what is done submitting the form as is shown in the first page where they can enter their details and navigate through the taps whether they were able to navigate. So client only gives you high level requirements like select the products in that card add items in the card and display them and check out bids and select the country to deliver and complete purchase. That's it. He will just give you a high level requirement and so what do you do to derive all positive and negative test guesses from these requirements. All right. So you have some basic idea on what are the requirements for you were testing now next phase. Is it test planning. This is the most important phase in the software development lifecycle and you will get a job if you are a Q A LEAD our manager have done successfully display. So how the job of the US is related to this will see in our next lecture okay. So basically I'm trying to showcase everything what happens and you are back and maybe you are not avid but all this may happen and sometimes you might be expected to attend these meetings are prepared a test plan so you should know in and out everything about QE so that you can handle and manage your projects. Maybe not today but tomorrow you will definitely go to that role and at least if you can show the skills that you are managerial skills are senior level skills with the course inputs whatever you are taking it would be easy for you to get promotion and to get granted to the higher level. Okay so in the next lecture let's talk about what happens in test planning face. All right. Thank you.