STLC

In the last topic we learned about the basic terms, and in this topic we will learn about Software Testing Life Cycle. In this lecture we will learn how software testing life cycle happens. How many phases does it have and what is the importance of each phase? What are the activities that happen in each phase? And after every phase what do we deliver for that particular phase?. Software testing life cycle is an integral part of the Software Development Life Cycle. Like there is a life cycle for software development, there is a life cycle even for testing as well which we will study in this. All the aspects of STLC phases which are there in it, we will see that because if any error is generated in the entire program. In which better way we can test it so that we can Find all the errors and we can fix it. So, there is a simple question here. What is STLC? STLC is a process in which we do different activities. Why do we follow those activities? So that the quality of the product is improved. STLC process is executed in a planned and systematic manner. First let’s see a figure of the phases of STLC so that it stays in our minds. The first phase is Requirement Analysis, after that what will be there, Test Planning, after that Test Case Development will be there, test cases will be made. Environment setup will happen in which we will test. Then in that environment all the tests will be executed. And then our test cycle will be completed. All these are the phases of STLC. Now we will see each phase in depth. Requirement Analysis is the first phase. Like you can understand from the name, what we will do in it. In this the testing team will study the requirements. The QA team will interact with the client. So that all the requirements are understood in detail. Now there can be 2 kinds of requirements in it. One is Functional and the other is Non-functional.  Now you will think which would be the functional requirement and which will be the non-functional requirement. Functional requirements will be those that will be the work that the software will do. Will the software be doing the billing calculation, is the software recharge application? Right? And what will be non-functional? Non-functional means what will be the performance of the application, how it will be? And the second is that how secure is the application? If someone is making a banking application, that application should be secured. In non-functional all these requirements will be analyzed properly. Now, in requirement analysis which are the activities that will be performed? We will see that. In requirement analysis we will see which all testing will be prioritized? Which test environment will be developed for us? Do we have to test this particular product or application in Windows, are we launching it for Linux or for Mac. In the particular process or product automation will happen or not. All these activities we will do in requirement analysis. Then what will be its deliverable? Its deliverable will be Requirement Traceability Matrix. Now, you think that what Requirement Traceability Matrix is? Come, let's see a demo of what is Requirement Traceability Matrix. Now the image that you have in front of you is of the Requirement Traceability Matrix. What is the 1^st column? Requirement ID. Every requirement will have an ID, so that we can identify it in a unique way, to know which is the requirement. Then what will happen, the requirement will be written. Then there will be an ID of its test case. That this particular requirement is there, how many test cases are there of it. Are they 5 or 6, they are there from where to where, 1 to 10, 1 to 15, 1 to 5, that we will write? What is its priority and what is its risk? Like, we will take the 1^st example, the system shall generate payment adjustment reports. Right? Now there are payment adjustment reports, for any billing software, reports are highly important. Right? So, what is the priority of it, it is of a high priority. And why is the risk low? Because we have to remove the payment information reports from it. Somewhere the payment is not getting affected. So, the risk is low as we have to only generate the reports. We have to design a query in the backend and generate the reports. Now we will talk about the planning. In this the senior QA of testing will play the role and he will tell us what is the cost involved in it, what is the time that we will take and what are the resources that we will be requiring? That planning will happen. The testing team will be finalized. In the testing team have we taken 2 or 3 testers and what are the skills of each tester? That will all be decided in the Analysis and Planning phase.