Thank you, Kathryn, for that introduction. Now, let's take a look at qTest manager and what we can do inside of it. The first thing that I want to cover is introducing the modules that you talked about in the beginning. In the top right corner, we can find the navigation bar.

This will allow us to find all of the modules that make up the qTest platform. Today we'll be focusing on qTest manager as 90% of the activities that we will be conducting. And the qTest platform will happen in here. Things like test planning, requirements management, test design, test executions, and defect tracking will all happen inside of qTest Manager.

One of the first areas that I want to point to is the project dropdown menu. Here we will find all of the projects that we have access to as a qTest user. At the moment I only have access to one project, but as a user, we had access to multiple of them. We can all find them here. Let's go ahead and take a look at this project specifically and how we can start creating or test plans, associating requirements, and creating test cases to satisfy those requirements.

As you can see, under my test plans, I already have a couple of releases created. One of them is mostly for automated executions and the other one is a regular release that I've attached requirements to and that we want to test against. Let's go through the process of creating a new release and see what that looks like. In the left corner, we can create a new release.

I'm going to go ahead and name this. And in here we can start adding all the details for this release, like the status, whether it's planned, in progress, or completed. Let's call this one in progress and also the start and the end dates, depending on how long we want this release to last. We can give this a brief description and now we can start associating requirements to this release. In this case, I already have a few requirements created.

I have separated my requirements by the type of application that I'm testing. In this case, I'm testing a mobile application, a browser application, and also a billing system. I can go ahead and open up those folders to find the requirements that I have already created.

And very quickly I could associate a variety of them with this release.

Once they're associated, the traceability between them will be permanent and we'll be able to report on these later on when I showcase qTest insights. Let's go ahead and click on one of these requirements. I will save it since we've done changes to the release and this will guide us to the requirements tab. 

Comments are closed.

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
Pen