Software Test Life Cycle-STLC

hello everyone I welcome you all to my youtube channel software testing by embedding in this video we are going to talk about very important topic in software testing which is called as what do you mean by SPLC also called as software test lifecycle so let us get started so SDLC is a step by step procedure or a standard procedure to test any new software that is called as software test life cycle it is a step by step procedure or a standard procedure to test any new software that is called as STL C now if you guys remember my sdlc video software development life cycle video if you don't remember anything link is in the description please check it out and please come to this video so if you remember my HD is the video so this s TLC is a part of my SB L see my hdl-c is a part of this DLC and my defect tracking my defect tracking is a part of my steal see so my defect tracking life cycle or birth life cycle is a part of my software test life cycle and my software test life cycle is a part of software development life cycle now the various stages in my software test life cycle are requirement direction and then system study this is my first stage of my software test life cycle which is called a system study system study is nothing but when customer gives the requirement our company product manager will collect the requirement come to our company explain the requirement or technical thing that is both the developer and test engineers making our technical team understand the requirement is nothing but system study it is asperity of the requirement to make our technical thing that is developers and test engineers making them score only understand the requirement it is nothing but system study and now my second stage of my SP is nothing but test plan test plan my test plan is nothing but all the future testing related activities it is nothing but how many the stingers are going to work on this particular release which test engineers is going to work on which particular module how many days my testing years will take to complete this product testing process for this particular release and which both include which we are going to use for this particular release which automation tool we have to use for this particular release so these are all things will be the part of their plan it is the plan it is a document which covers all future testing related activities now the third stage of my SPLC is called as write test cases and then write excuses we are having multiple stages which is called as systems reading again now what is the difference between this system study and this system study this is the system study which will be done by the be a business analyst or the project manager where it will give the complete knowledge of the product complete requirement knowledge we will give to the both developer and test engineers he will make all the technical team or all the people present in the company understand what is the requirement coming to this system study this is nothing but it is a system study which will be done by individual test engineers suppose there are five test engineers and each are assigned with a particular model like a model is going to testify - test engineer B model is going to test by my this test engineers same order is just by my disgust engineers so this system study is nothing but each and every individual test engineer whatever the model is to that particular test engineer he will study or he will try to understand that particular model in detail that is called as this system sorry once after my system study is done we have to identify all possible scenarios so I will define possible scenarios identify all possible scenario is nothing but whatever scenarios I have to test my application that scenarios we have to identify each and every individual test engineer we identify all possible scenario to test the particular model which is assigned to him in this the third stage is called as write test cases here they will write all test cases after writing test cases they will make it review then we get it reviewed once after review is done we have to do 6 review comments fix review comments once after fix the new comments are done then we are we have to get approval once after approval is done we have to store our test cases means test is repository tool so unless is the right test business de or other stages now once after my test is part is done we have to write traceability matrix we have to prepare the traceability matrix the other means of traceability matrix are also called as a requirement priscila T matrix and also cross reference method now what exactly is my disability matrix traceability matrix is a document which ensures that each in every the requirement has got at least one test cases in it when we are having the list of requirement when we are having all the list of requirement we have to make sure that each and every requirement has got at least one test users in it that is nothing but traceability matrix so we will see the requirement and we will see for each and every requirement there is particular test cases there or not if any of the requirement has not got any particular test cases then we can go and mark that requirement and if other requirements have got at least one test isn't it we can unmarked it so this is called as traceability matrix now there are three types of traceability matrix we have the first type of Chris ability matrix is condensed forward traceability matrix which is also called as horizontal traceability matrix forward triste ability matrix is nothing but here we ensure that each and every requirement has got at least one test cases in it or not our traceability matrix is prepared before our test case execution so once after metastasis is done we will prepare the traceability matrix once often traceability matrix is prepared finally we are going to do the test case execution this is what happened in forward disability matrix which is also called as horizontal traceability matrix while doing horizontal traceability matrix of forward traceability matrix here we ensure that our rebuilding product right the second type of traceability matrix is called as backward traceability matrix or vertical traceability matrix in what backward traceability matrix here we ensure that here we map the test cases here we map the test cases to the requirement here we ensure that the scope of the requirement is not changing the scope of the development is not changing whatever the requirement was given by the customer same thing developer is implementing nothing is changed in backward the D matrix we ensure all these things and backward traceability matrix is prepared once after test execution is done and most important help ensure that our rebuilding right product so the main things which you need to remember is for our traceability matrix is prepared before my test case execution and backward rigidity matrix is prepared after my test this execution and the third type of traceability matrix is called as bi-directional traceability matrix it is a combination of both forward reciprocity matrix and my backward precipitate matrix so once after I traceability matrix is done as I told you once after my traceability matrix is done we will do test is execution we will do execution test is execution is nothing but you will be having a set of test pieces with you and you will be having your application by looking into the test cases you will test application and mark the test cases as paths are filled so that is nothing but test his execution once of remaining test execution is done the next page of my STL C is corners defect tracking now what is defect tracking link is in the description please check it out I will explain each and everything if the feature and functionality is not working according to the customers requirement then queue way all our testers will raise the different which is nothing but defect racking one software defect tracking is done the next stage of STL C is called as test case execution report this is a report which will be prepared by our test lead in which he will he will prepare the report telling that which test engineers were was involved in which particular module testing and how many books we have found out how many test cases are in the past Pettis how many test cases are failed what is the past test his percentage all the report you test his execution report and the final stage of my stsc is called as retrospective meeting post-mortem meeting so retrospective meeting on course part of meeting it is a meeting conducted while my test manager where he will invite all the test engineers who were involved in particular release and he will mainly discuss what went well what didn't go well what are the mistakes we have done whatever the achievements we have achieved how we can improve the process these are all things we will discuss in the post-mortem meeting so this is the various stages of SPLC I have tried to explain in a very easy language if you have any question related to this video please ask me in the comment section if you want to reach to me or personally I have added my gmail in the description please check it out if you think this video was useful to you guys please share this video with any difference like this video subscribe to my channel software testing bioody

Channel: SoftwaretestingbyMKT

Views: 88,861

Rating: 4.9395628 out of 5

Keywords: software test life cycle, STLC, software development life cycle, software testing, sdlc, what is software test life cycle, SDLC VS STLC, Software testing, sdet, qa jobs, QA Engineer, Software testing future, phases of testing, softwaretestingbymkt, MKT, software testing by mkt, test life cycle, what is api, what is scrum, what is smoke testing, what is software testing, why should i choose software testing as my career, manual testing, automation testing, software, IT jobs

Id: UjpZHRVJWgQ

Length: 11min 18sec (678 seconds)

Published: Wed Oct 02 2019