You can refer to quick steps below to start using qTest Pulse easily.
Step 1. Access and Logging In
First, you need to have an active qTest account with access to qTest Pulse. Users will need the Administrator user profile or you can a new profile with only Pulse access. A qTest Site Administrator is required to do this. Here are the steps to create a new profile: steps. Check the Pulse access option as shown below.
After the profile is created, users will need to be assigned this profile in the Licenses - Users section.
Once you have been granted access, you can access qTest Pulse from the 9-box icon in the top right corner of the navigation bar.
Step 2. Create a Team
To use qTest Pulse, you must below to a team. A team is a group of members who have access to the same projects. Pulse will prompt you to create a new team. Any user who does not belong to a team will see this prompt. You will be the team owner for any team you create. If you should belong to another team, contact that team’s owner.
Users who already belong to a team will land on the Activity page. Click here to learn more about the Activity page and Work Items. You can switch to another team by selecting it in Team drop down right next to qTest Pulse logo.
Step 3: Create a Project
All of your work items belong to a project. A project shares the same set of configurations, integrations, and rules. It is recommended that you have one Pulse project per JIRA project. Click here for instructions on how to create a new project. Once a project is created, you can configure JIRA and GitHub to work with each project.
Step 4: Configure JIRA
This step is not required but is highly recommended. When qTest Pulse is integrated with JIRA, work items in Pulse are automatically synced with items in JIRA. The projects, issue types, and events that happen based on status changes in Pulse or JIRA are all configurable. To learn more about this integration and to configure it, click here.
Step 5: Configure GitHub
This step is not required but is highly recommended. When qTest Pulse is integrated with GitHub, all of your test cases will be stored and versioned in GitHub. If your continuous integration (CI) tool, such as Jenkins or Bamboo, is integrated with GitHub, test run results will trigger new builds and reported as xUnit or JUnit. This gives your executions the ability to fail your automated builds. For configuration instructions with GitHub, click here.
Step 6: Invite Other Members
On the Teams page, you can invite others to join your team. They must already have an active qTest user account. To add members to a team, search for an existing user and select them. Once selected, you can assign them the Owner or Member role. Owners can edit team settings including integrations and invite new members.