Introduction to Software Testing Life cycle

A free video tutorial from Rahul Shetty
Teacher over 600k+ QA Students|Founder of RahulShettyAcademy
Rating: 4.5 out of 5Instructor rating
29 courses
633,840 students
Introduction to Software Testing Life cycle

Learn more from the full course

MasterClass Software Testing with Jira & Agile -Be a QA Lead

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

10:18:18 of on-demand video • Updated November 2022

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 (Project management tool) and Tester activities in the Jira from Scratch
Thorough knowledge on latest Practices like Agile scrum, SDLC, Testdriven, Behaviour driven approaches
In Depth knowledge on writing test cases in Jira using Xray app on Live Project
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
Top 50 Frequently asked Software testing Interview questions with Solutions
Basic knowledge of SQL
English [Auto]
Welcome back, guys. So in this section, let us look into software testing lifecycle. So, first of all, you need to understand that testing is not only limited just to find books. Many people are in assumption that what you at best, they will just test an application for that. That's it, right. What's the special in that Queiroz? But that is not true. We have equal 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 Cuba. If this is a simple job that everyone can go and test an application. If that is not really matters, then whyever testing does still exist in the market. So, for example, let's say you have developed a billion dollar product. OK, so will you do risk by asking developers to do testing when you have a product? Billion dollars. What if that goes wrong all over? Money will go in to them. OK, so similarly, people may tell you that testing will go away, but it won't go away. OK, so if you have at least one million dollars and if you are trying to implement one project, you will never let that project go without proper testing from Cuba specting. OK. It's just that if people do that work, but do not believe that. And you also need to know that it's just not limited to find bugs. So let me explain you the lifecycle of the test of when they are in the project and how do they perform activities on indictor project. In the last section, we have seen how a test done was in one specific spring and the agile scrum environment. Now, in general, what does Bestor and Cuba have responsibilities in the project in general, not specific to one spring are not specific to one iteration overall, starting from the project and finishing up the project. What our tester does and how he plays a key role in that all that options, we will be looking as part of this action. And we call the whole lifecycle of our 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 your job. Starting from requirement analysis until Tester the. Now, I will go through each and every phase of this lifecycle and explains what does a tester do in that particular phase for their project. OK. Now, the reason why I have done this point that it's not limited to find books that will involve in every phase of software development. OK, not just testing an application. OK, so now let's get deep dive into each and every phase and try to understand what are our roles in each and every phase. And how would we need to solve all the challenges, whatever we face in all these stages? OK. First, requirement analysis, the CuIt team, that means testers will interact with various stakeholders like a business analyst product on a 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 your team and given some requirements that you need to build as part of the software. Let me take you to one website, Rockhole Shakti Academy dot com slash angler practice, OK? Let's assume that me rajul here is a client. I have approached one team asking to develop this application for me. OK, so basically this application is all about filling the form and click on Submit. So user need to enter their name, email, password, gender and data so that their user details will be stored in my database and then they can shop the products. You can click on this shop that and you can actually select the items you want to buy. So that when you select here, the items will be added to the. You can see that check out three items and just basic ecommerce app. So once you have selected items which you need to buy, and then you will go to check out page. And in the checkout page, you will see that all the details, like what are different products present here? And then if you want to increase the 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 it will be taken to this page. And you need to. Which country you want the best products to get delivered? If you give India, then that option will public from this dropdown and you need to read the terms and conditions go and parties of a simple e-commerce application. So this is what I need to build. So when I approach development team. So basically, I won't have all these business. Right. All of this will be prepared once the project is delivered. So client will appeal verbally. He will draw some diagrams, build some prototypes to show how his application should get developed. OK, maybe once again. Right. So you need to interact with either client if you want to directly talk with them or you can talk and interact with your product owner or business analyst, sit with them first to understand requirements to develop the product. Most people will be an assumption that only developers will sit in that meeting to understand what to develop. But that is wrong. Estus also should go to that meeting and try out to understand all the requirements. OK, 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. OK. If he if he or she is not attending this meeting, they should just depend upon what developers say about the application. OK, so you need to attend this meeting to understand it from a client perspective or product or another perspective, and then have your own planning or design after your test gets us for testing that specific product. So basically, if you are a normal software engineer, the best engineer in your team, you may not be called to this meeting in general. Q Lead manager will address this meeting, not all like you, who are present in the team. So there 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 the junior or mid-level in your company, but talk to your manager and they will definitely tell you that this meeting should happen before any project kick started. So in our case, I assume that I am the client and I am asking to develop this whole application for me building this products and everything. OK. So from that meeting, you have to get these requirements first, business requirements. You have to not be done submitting the form either on the first page where they can enter the details and navigate to that baps, whether they were able to navigate. So client only gives you high level requirements, like select the products in the cart, add items in the car and display them in checkout page and set up the country to deliver and complete passes. That's even just to give you a high level requirement. And you're still a duty to derive all positive and negative against us from these requirements. All right. So you have some basic idea on what are the requirements for Uber testing. Now, next phase is a test planning. This is the most important phase in the software development lifecycle. And you will get a job if you are currently our or manager to have them successful test planning. So how the job offer us is related to this will be in our next lecture. OK. So basically, I'm trying to showcase everything. What happens in your back and maybe you are not aware, but all this may happen. And sometimes you might be expected to attend these meetings or prepare a test plan. So you should know in and out everything about it so that you can handle and manage your projects. Maybe not today, but tomorrow. You will definitely go to that goal. And at least if you can show the skills that you have, managerial skills are senior level skills with the course inputs, whatever you are taking. It would be easy for you to get promotions to get transact with a higher level. OK. So in the next election, let's talk about what happens in this planning phase. All right. Thank you.