SmartBear QAComplete

Key Features and Benefits

• Improves team collaboration and effectiveness by connecting QAComplete to third-party tools and synchronizing artifacts across the software delivery lifecycle

• Synchronizes failed tests from QAComplete to defects in Agile tools

• Streamlines test development by synchronizing requirements from requirements management tools or user stories from Agile tools to QAComplete
• Enables cross-tool traceability and consolidated reporting by collecting activity data from QAComplete and other tools into a central data repository
• Integrates DevOps and automated testing tools (like Selenium) with QAComplete, automatically creating defects in QAComplete when tests fail

Common Integration Patterns

• Sharing Stories and Defects between Dev and Test
• Providing Developers with Early Visibility into Requirements
• Providing Testers with Early Visibility into Requirements
• Aligning Testing Teams across Testing Tools
• Populating Requirements into PLM Tools

Demo Videos

Minimal User Permissions & Hub User

We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization. 

In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.

Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository connection utilizing a weak password/token, such as 'tasktop.'

See instructions on how to create a new user in Smartbear QAComplete.

List of minimal user permissions:

• User must be added to a security group that has read, add, and update permissions for the artifact types being synchronized.

• The group should also have read permissions for Manage project creation and setup, Manage user accounts, and Manage custom fields.
• To synchronize relationships between artifacts, user must have permission to Manage and view traceability (links between items).
• To create and synchronize artifacts, user must have permission to Manage workflow and state transitions.

See the example below:

To create a new security group, go to the admin view (by clicking gear icon in upper right). Then select Security → Security Groups from the left panel.

From here you can add a new group (the + button on the top toolbar) or manage an existing one (the person with a lock button on the left side of the row).

Connecting to the SmartBear QAComplete Repository

Standard Authentication

Required Fields:

• Location/Connection URL
  • Example Format: https://rest.qacomplete.smartbear.com
• Username 
• Password

Optional Fields:

• Throttling Settings: This field indicates the number of API calls that can be made per minute. See details here.
  • Note: This field should only be set under the guidance of customer care as the ideal value is highly dependent on each customer's unique environment. 
• Connection Security: If checked, insecure connections to this repository will be allowed. See details here.

SSO Authentication

Additionally, SmartBear QAComplete supports the following SSO implementations:

• Script (HTTP cookies)
• X.509 Certificate

Learn more about how to set up your repository in Planview Hub here. 

Comments

The 'comments' section in SmartBear is not the field that flows when Comment Flow is enabled within Hub.  When comment synchronization is enabled within Hub, the "Notes" section in SmartBear will be used as the source and the target destination for flowing comments.

In summary:

• Comments: Treated as a simple rich text field

• Notes section/records: Treated as comments for collaboration

  

Learn more about how to configure comment flow in Planview Hub here. 

Person Reconciliation

For person reconciliation, the following fields are available:

Learn more about how to configure person reconciliation in Planview Hub here.

Full Scan

Due to third party API limitations, updates to the following fields may not trigger change detection or cause a synchronization immediately. To ensure these updates synchronize, a high fidelity full scan must occur or another qualifying change must be made to the artifact:

• Relationships (Multi-Links) in QAComplete versions 11.4 - 11.7

Learn more about how to configure change detection and full scan intervals in Planview Hub here. 

Special Features Supported

Supported Work Items

Learn about the difference between containers and work items in Planview Hub here. 

Supported Containers

Learn more about containment in Planview Hub here. 

Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not synchronize properly.