Welcome to the qTest Pulse Quick Start Guide. The article is meant to walk a user through how to access qTest Pulse and configure your first project.
Access and Login
First, you must have an active qTest account with access to qTest Pulse.
Your qTest Site Administrator must create a new Admin User profile with qTest Pulse access selected. The default Administrators profile (located on the left navigation tree) should have qTest Pulse access by default.
- Select User Profiles from Site Administration and add Pulse Access to an Admin user profile.
- After the profile is created, they will need to assign this profile in the Licenses - Users tab. In the example below, I have two users that both have will get access to qTest Pulse even though they have different Admin profiles.
- AJ Ford - "Administrators"
- Ali Huffstetler - "Pulse Access User"
Once you are granted access, you can log in to qTest Pulse from the 9-box icon located in the top, right corner of the navigation bar.
Create A New Team
Teams in qTest Pulse are areas where collaboration occurs for your projects. For example, you might have one team that's dedicated to testing a web application and another team that's focused on cloud deployments.
These teams will likely work in different projects and have different configurations.
If you do not own or belong to a team, the qTest Pulse will ask you to create a new team. If you are a member of a team, you are automatically redirected to the Activity page where the work items of the team to which you belong are displayed.
You can switch to another team by selecting it the Team from the drop-down next to the qTest Pulse logo. Click here to learn more about the Activity page and Work Items.
Create a Project
All your work items belong to a project. Work items could be issues from Jira or created directly within qTest Pulse. Create a project for your new team, and then configure Jira and GitHub to work with the project. 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.
To learn more about this integration and to configure it, click here.
- Select gear settings icon
- Select your project name and then chose ALM Software
This step is not required but is highly recommended. When qTest Pulse is integrated with GitHub, all your test cases will be stored and versioned in GitHub. If your CI tool is integrated with GitHub, test run results will be outputted in a test runner output and trigger new builds. Failed test cases will show as automated testing results and will be reported in your build report.
For configuration instructions with GitHub, click here.
- Select gear settings icon
- Select your project name and then chose Version Control
Invite Other Members
On the Teams page, you can invite others to join your team. These individuals must already have an active qTest user account. To add members to a team, search for existing users and select them. You can then assign these users to the Owner or Member role. Owners can edit team settings including integrations and invite new members.
- Select teams from your user avatar and click the edit icon next to the team wish to add members.
- This From this screen you can add members that are associated to the qTest Licenses - Users area in Site Administration.
- Owner Access: Full admin access for qTest Pulse teams
- Member Access: Access to project level activity board
- API Access: Read and write abilities to the qTest Pulse API
- From each team view, you can also add more projects.