In the Requirements Tab, I will find all of those folders that contain the requirements that I have created. And in here I can also create new requirements that I would like to add to my releases.
Let's go ahead and select my mobile application and create a new requirement. All these requirements for just to be simple. And again, we can start adding all the details for this particular requirement, whether this is new, in progress, or baseline. Again, we'll call it in progress.
This will be a must-have priority and we'll call this a functional requirement. Now, since I'm the person who is creating this requirement, I can go ahead and assign it to myself. Or if I'm a QA manager, I can go ahead and assign this to the particular tester or QA personnel that I want to oversee this particular requirement.
I'll go ahead and give it a description. And now that we have our new requirement, I can go ahead and either attach it to the release that I have created, and then I can start adding test cases to satisfy this requirement.
Now, I may already have test cases that are designed to be able to test this, and I can find them really quickly by going into my test case folders and finding those tests that I have already created. As you can see, I have my test defined by their type.
So I'll have a folder called integration tests, one for unit tests, one for functional tests. We can have one for performance. And these structures are really up to the user on how they want to structure their teams and the QA practice.
If we're looking for some best practices and how to structure this, we can always find them in our documentation. We actually have a pretty good article that details a variety of ways that we can organize ourselves and our teams, whether we're following a waterfall methodology, whether we're doing it by an agile methodology, by releases or sprints, or maybe we have a more complex system with multiple products.
I want to learn how to organize those. These are clear examples of how we can structure these, which mainly come into play once we're reporting later and insights as depending on how we're splitting our tests and our requirements, we can very quickly filter through that data once we are reporting.
Coming back into qTest. Let's look at or link the test cases area. Right now, we don't have any test cases that are linked to this new requirement. However, I can add them in here or if I haven't created those test cases, I can come to the bottom and be able to show or create what I call a test case shell. We can give it a quick name.
We can also give it a type and a brief description. And once I create now we have that new requirement or sorry, this new test case that I can develop further. I can go ahead and click on this test case and save my new requirement, which will bring me to my test case tab or my test design tab.