Whatever client requirements we have received, we will do an analysis of it. Let’s see what the requirements are given to us by the client. We are assuming that our client has some technical knowledge. Come let’s see what requirements the client has given in a document? As you can see, Client’s name has been given in a document. Which is the project of the client? It is through the requirement form an e-commerce website. Where the client is saying that he wants to launch this website globally in all the countries. On one email, one user only, that means, for one email only one user login should be there. Only Paypal is needed for payment integration. Then he wants only DHL and FedEx as his shipping partners. There should be two logins for buyer and seller. There is a requirement of 16GB RAM. And he has kept the purchase limit of a shopping cart as 50,000. That means that if the customer goes over 50,000 he will not be able to purchase. So, this is an average requirement that is there with us, we will do an analysis of these. And we will see ahead what will happen in our next cycle. Now we will make a Traceability Matrix. The first question, what is this Traceability Matrix? This is a document which will be mapped with the requirement specifications and this further we will map with a test case ID. Let’s imagine that R1 is a requirement and its T1 is a test case. So, we will map R1 and T1. The importance of this document is that all the client requirements should be covered and we can give surety to the client by showing this RTM about the completion status of this product. Now we will see how we will make the Traceability Matrix. Here we have taken an example of a requirement of login and logout which we have further divided into modules, application role and descriptions. Like you can see on your screen, one requirement we have taken in a table form which we have named as B1, module name is Login and Logout, application role, means who will use this role, that will be Manager. We have given a description for that, who will be the customer and who will be the manager. Now going ahead, we will divide the requirements technically. Since we are deciding the requirement technically, we have mentioned “T” before every requirement. We have mentioned “T”, so that we get to know that this is the division of technical requirements.
In the test case in a column, we will add TR and we will print T94 there. Now we will see ahead what will happen. Like we have written T94, which is a technical requirement. Now we will match this technical requirement with the business requirement. Which was our B1. We will add that requirement in the test case in the BR column. You can see that in the test case only 2 new columns have been added, that is BR and TR. So, the B1 requirement that we had technically bifurcated that was T94. Now think how will the Traceability Matrix look. Let’s see the Traceability Matrix. B1, T94, Test Case ID, 1. What happens with this? With this we will easily know which are the requirements that have been completed, with which requirement, which test case ID has been mapped, which requirement has which technical ID and it is easy to analyze it further, how the requirements should be further divided. So, this was our Requirement Traceability Matrix. How to write the Test Case? We have read the scenario so now we will prepare the test case based on that. Like our 1st test scenario is that, if the user is not logging in, how will we test that. In short, the test case is that detailed description, the functionality that has to be used and its output, what will that be and what it is that is coming. Come, let's see a live example. Now we will put in this wrong user name. I have entered a wrong user name. It is saying please enter a valid user address. Okay, so the functionality is giving us the output. Come, let's test it by entering a valid email address. See, it has been accepted. Now what will we do? We have put the correct user name. We will enter a wrong password. Okay, let’s say we entered a wrong password, so what will be the output? What is it saying? The email and the password you entered don’t match. Keep in mind, a lot of kids make mistakes in it. Always the database goes in the combination of username and password. If not, identify your username and password separately. Right? So, pay attention that if the username and the password is not the same, you will get such output. The email and password you entered does not match. This is a detailed example. Here TC1 is given as a login page. How to test the login page. How to execute steps for that. What test data to be used and what will be the expected result. Let’s see about the Test Suite. Like we use the suitcase, right? What is there in it, our small bags or our luggage. Similar group of test cases we keep in a suitcase which is called the Test Suite. Like there is a login suite, in this we will keep every test suite that is login related. This will make it easy to test any functionality. Now, in the next topic we will see about Software Development Model.
Course is very good but do we get any written notes along with it >??
Lawal Adewale David
LearnVern gives a deep view of software testing. This is one of the best learning platforms out there. Keep it up.
very nice. keep it up
Very well done courses
Cover all topics
Vinayak Vijaykumar Savle
it was helpful
very nice explanation and in depth knowledge
very nice explanation and quality videos, in depth knowlege of subject
Learn Vern is good platform for learning n gaining the knowledge....