Create Attestor Required with airSlate SignNow

Cto2 form

hi everyone this is swathi from the software testing hub dot counting and in this segment we'll talk about requirement traceability matrix now requirement traceability matrix is I say this one of the topics that I find hardest to teach not because it's complicated on the contrary it's one of the simplest concepts but the reason why I have a really difficult time teaching it to a live class is because there are different opinions to different you know different different students or different people have different opinions of on what an 80mm is where it should be used or how it should be used now I wouldn't like to contradict any of them because all are very valid points are in very different ways of representation and you note two very different ways of interpretation which is awesome variety is the key to an interesting class which makes it awesome for me to discuss the topic so in this session I'm going to share a few of my experience with experiences with REM and the way I approach RTM and the way I see a requirement traceability matrix can be built the way I've practically implemented it and I would like to share and then open up the forum for any of the other opinions or any views that you might have so technically any technical term I believe can be understood very very simply by actually understanding what it's what its literal meaning is now matric is nothing but a row called matrix is a row column combination in other words it's simply a table right like any other table that you create in an excel sheet now traceability is basically being able to know from where you come and where you're going so it is like creating a trace literally and then you're trying to establish a trace for your requirements because the reason why RTM exists is because of an inbuilt need for testing engagements to satisfy the 100% test coverage rule so let me actually show you a pack example traceability matrix that is also available on our website so let me actually define again so it's a matrix which is a row column combination just like you know a simple table that you are seeing on my screen and it is there to establish traceability so you exactly know where you're coming from and where you're going and we start with requirements all the way to everything else which we will see in the little in a little bit and an RDM is basically created to make sure if the testing engagement is following the hundred-percent test coverage rule or not so one of the first things you know raw materials for us to start testing is requirements correct now these requirements how do they come to us they come sometimes in the in the format of a B ID now business requirement document strictly speaking should contain only the business requirements as you get them from the client but then you know sometimes a B refr D and TDD are all together merged into one as one requirement document and that's okay because as long as requirements are returned in some form it doesn't matter whether we are segregating into a separate business functional or technical requirements so all of these requirements come to us in one form or the other so let's say let's refer to all of these documents as you know whether they come as one or many as the reference documents and the next thing in another way the requirements can come to us in the form of use cases sometimes these use cases are part of the BRE of our DTD documents but sometimes they are also independent documents so they can come to us in the form of use cases in the form of wireframes are sometimes informally in a meeting they might be given to us verbally so all of these are different ways in which you can or we can actually identify or gather the requirements so once you have half the requirements as testing teams what do we do we sew requirements are like the raw material following the requirements what we do is we create something called the test scenarios which are the intermediaries for us to get started with the rest of the testing process so a test scenarios have one line definition of what we are going to test so let's say if the requirement is Gmail compose email functionality and this is requirement number one and then you will you know list out what is it that you will test in each one of this so you will check for composing or you know trying to send an email with blank text or you know blank body of the email don't write anything and try to send it explore try they are rich - rich text options right for the body of the email no subject again of course you're going to elaborate it I'm just trying to give you an idea no subject no email addresses in the to list so all of these are possible things or you know one-line pointers of what you would check so typically what we will do is we will give them an ID so this is related to composing an email and serial number correct so this one requirement has four of course many but for now it has four you know it has four test scenarios that we've added different but of course these are not enough for us to go ahead and test we need to have detailed test cases so test cases we normally address them as TC underscore compose email underscore zero one so for the first test scenario check for sending an email with a blank body I'm going to write exact sequence of steps like first login then click on compose email do not enter any text in the body enter a subject and enter a address or to address and then we click send so detailed step-by-step process there are many other fields that can be included the data should be included everything else that you get the picture so similarly we will have will write this kind of test cases so you see when we when we are moving from requirements to stress scenarios there might be a one to one so one requirement gives results in to multiple test scenarios so a requirement to test scenario ratio is mostly one to many but it might be one to one as well similarly test scenario to test case it may be month one to one or it may be one to many so one requirement will result in multiple test scenarios and one test scenario will result in multiple test cases so a simple requirement traceability matrix if we were to make sure that you know all the elements of testing has been followed from the requirement all the way to test cases you start creating an RDM so atom will have the requirement ID for this simple example a requirement ID a test scenario ID a test case ID so for one requirement requirement number one you have ended up with four test scenarios and for first test scenario you have this particular test case so if you have further test cases for these you will go ahead and add these so if let's assume there is a second our you know a requirement for which there are again many other you know test scenarios now how do we use this document let's for example say there is you know other test cases return for this all right so let's say these are 3 & 4 that are returned for this hypothetically and then when you look at this there's a gap here so this shows that this particular test scenario has not been addressed in test cases so let's assume there is another you know requirement requirement number 3 that has all of this stuff again and then let's say this is the traceability matrix you ended up with since you know number one requirement has been addressed in these many test scenarios in these many test cases three also has been addressed in doubt all of these ideally there should not be a gap here so let's actually fill it so when you see a gap like this it shows that this requirement has not been covered so this is the way in which traceability matrix can be used but as I was saying lot of times is a confusion on this topic because they usually some you know another school of thought is before you even write these tests in areas and test cases you actually start creating an RDM document with the requirement ID you will start with one go ahead and write your test scenarios and as soon as you write it you come here and you know update this sheet so RTM is done along with this documentation I for one don't see a lot of value in that because to create an RDM you will need all this raw material all these IDs so for me without those ID is going back and forth between nrt m and the documents is kind of you know a waste of time and I feel like I'm all over the place so that is why I like to create an RDM after I'm done with all the documentation as a checkpoint to see whether I am following the 100% test coverage or not so quickly so this is simply an a-t-m you can actually color code this make it look fancy but at its core this is the simplest way to create a Natyam now if you were using a test management software like QC or you know Q test or anything else you don't have to explicitly create an a-t-m because traceability is an inbuilt aspect of the tools but even if you do have to create it manually you have just seen how simple it is so this is a traceability matrix that we have on our site now this is for a project where there is an F Rd so you can actually take a look at this the business requirements are defined in a way that there is section 1 2 & 3 and in the functional requirements section 1 is elaborated again 2 is elaborated 3 Zillah sorry 1 is elaborated and it's broken down into 1.1 1.2 sections similarly there are some test scenarios that are written that have been written to it and of course there will be test cases that step isn't there but when you have to map it all in to test at an RPM the business requirements section one since you know the requirements are not ID'd they do not have an identification number we are using the section numbers as a way to reference back to them and the corresponding FST section is this and the resulting test scenarios are all of this and for each test scenario these are the test cases that are written so for some reason if all of this section is blank it shows that if all of this section is blank issue sorry it shows that you know requirement 1.2 has been completely you know ignored for testing activities but on the other hand if there is you know let's do this if for example there is a business requirement you know there but then nothing else you seeing from thee so this has not moved into FST this has not moved into test scenarios not moved into test cases now what this could potentially mean is this requirement that requirement number two has been D scoped but the PID has not been updated so this is also a way to see that I have do we have the right reference documents have they been updated or not have have the updated document being considered for testing so all of these things become much clearer when you are going to use an a-t-m now here in the test scenario I D have also used the test in on your description you don't have to do that the only reason why I choose to include it is because F have chosen to extrapolate the RTM into reading the status and the defects so I'm actually using this as a status report so since status report is sent to teams that are not exclusively QA teens it is a good idea to make sure that you know they understand what this code means but then you don't have to do that simply you know giving the numbers like we did here that should suffice but then you can actually expand it to read the status of each test case and actually provide the corresponding defect IDs now how you can interpret this how this can be much more useful when you include the defect IDs and everything is say when I say that the a defect ID one I can tell that this is affecting the loan process so that kind of extrapolation all the way to business requirements I will be able to do it seamlessly if I choose to include these two columns and Artyom is also not a deliverable to anybody it's just an internal point of check that the QA teams do so that is why most of the companies or most of the clients most of the projects they can just skip this process but then it's up to you it's definitely something that is worth investing your time on and it doesn't take long it's also a collective team effort everybody whoever is responsible for their particular requirements their particular test scenarios they all contribute to creating one traceability matrix so as a group effort it doesn't take more than an hour or so but then the you know benefits are you know self-explanatory you can always make sure that you know your testing is being effective and the coverage wise every requirement is addressed in the testing activity so as always please let us know if you have any questions or comments thank you everyone