Test case design development and cycle closure

Test Case Design and Development. In this phase we will design the test case, we will recreate the test case and we will identify which would be the test data for a particular test case. Which data we will use for the testing. Which all activities will be there in this phase? In this we will 1^st make the test cases. After that what will we do? Which all test cases we have developed. We will review those and after that for the particular test case, we will set up the test data.  Now what will be its deliverables? Test cases, Test script or Test Data. With all activity we have done, we will deliver that. So, that will be its deliverables. Now we will take an example of a Login Test Case. Like you can see on the screen that we have taken a test case example in which there is a Scenario, Test Case ID, Test Case Name, Test Case Description, for what is that particular Test Case made? Test Step number, what is the work of Test Step Description in each step? What will be the expected result?, what will be the actual result?, Status and Comments. This is an example that we are taking of a Test Case. As per different Projects there will be test cases. As per different companies, different standards will be followed. If they tell you to make a standardized test case in the interview. If they are telling you in the interview that you write a test case for a particular website or a particular login. So having these things are important. Which ones? Test Case ID, Test Case Name, Description, Test Step number, Test Step Description, Expected Result, Actual Result and Status. Now we will see what is there in the next cycle. Now there is Test Case Execution. As per the test plan we will execute the testing, we will report the bugs and tell the development team that all bugs are very important and crucial which we have to fix quickly. Which all activities will be in Test Case Execution? As per which we will execute the test plan. Whichever test plan is decided in the planning according to that we will execute all the tests. All the results like pass or fail, all those results we will document. We will maintain a defect log , in which all the documents that are failed we do their documentation separately. There will be one Requirement Traceability Matrix, as per which we will map the defects. And the defects that are fixed, we will retest them. These are the activities, now what will be its deliverables? The deliverables will be that we will check the status of Requirement Traceability Matrix. We will update the Test Cases with the results and we will deliver the defect report. Now there will be a question. What is the Requirement Traceability Matrix? No problem, we will take an example of the Requirement Traceability Matrix. It is very easy. First Of All What is the Requirement Traceability Matrix? It is one process in which we will map the requirements and the product that is getting developed. Like you can see in the example. The 1^st requirement is that the restaurant has 2 ordering stations. Its design is Management Screen 2. And its internal design is on page number 45. Its function or the code of this requirement that has been given as a line number. And we have given that on which test this requirement is tested. Which is the Test Case ID.  We call this thing the Requirement Traceability Matrix. So that it is easy for us to check, if there is this requirement, which all are the Test IDs which are linked to that particular requirement. So, we will execute those tests. So, this is the Requirement Traceability Matrix. Now we will come to the Last Cycle’s point which is called Test Cycle Closer. Testing team will discuss and analyze whichever defects are identified and in future which defects will be fixed. Current Test Cycle, whichever has happened. Is there any scope of improvement in it? Now, which activities will be there in it? In these activities there will be cycle completion criteria, has it matched or not, all the testing should get over on time, no critical issues should be pending. Like any critical bug that we have given to the development team to fix. We should test that properly.  We will prepare the Test Matrix; we will make a document about what we learned in this project. With this project and going ahead if these projects come then which strategy, we will follow in it.  Now, what will be the deliverables in it? One test closure report like which tests are passed, which ones are failed, which bugs are still open, which bugs are fixed and Test Matrix. Again, there will be a question, what is the Test Matrix? For this also we will see one example. And you will understand even that very easily. We can see in the example what is the Matrix that we have taken and what is its purpose and what is its defect category. To measure the testing quality there is a Matrix which we call the Test Matrix. Which all things are included in the Test Matrix? Let’s see that. In that there is defect severity, defect removal efficiency, what is the defect finding rate, test case execution statistics, test case effectiveness, what is the test coverage, what is the time taken to fix a particular defect, what are the number of defects that have come, in which all cycles which all defects have come, what is the severity of defects. All this information we will put in the Test Matrix. Last thing is Test Process Analysis. With all reports we have sent to the management, we will analyze that and see if in the future, is there any new technology or any additional feature which if we add, will that improve our process or our quality or not.