One-way and two-way synchronization:
- Test Configuration
- Test Set
- Test Instance
- Test Run
- User Story
- Test plan
- Test Plan Run
Test teams often rely on HPE QC and HPE ALM to provide the infrastructure they need to execute their work. But when it comes time to collaborate with teams and product managers who are using Targetprocess, then the fact that other stakeholders rarely work in HPE ALM can become an impediment. Integrating Targetprocess and HPE ALM/QC one-way or two-way can help you plan testing activities and keep track of important testing metrics.
Every integration case is unique, because you have to map your own special set of fields and work structure. If you’re interested, please check with us via firstname.lastname@example.org to get started with a demo.
- Testers need to see when product managers create project requirements and Features in Targetprocess in order to plan their test strategies and develop test cases. Synchronization between the two tools helps everyone to better plan testing activities.
- Testers create and manage defects in HPE ALM/QC, but development and product teams work in Targetprocess. With two-way synchronization, it's easy to keep all teams in sync.
- Product management teams working in Targetprocess may want to track portfolio and release progress by looking at consolidated defect and testing reports, but they need to be sure that development progress and defect reports reflect their current status. With an integration in place, there's no need to manually duplicate work in Targetprocess.