2
1/2 HP Quality Center - Atlassian Jira | 2012-06-01 agosense GmbH Stammheimer Str. 10 70806 Kornwestheim [email protected] fon +49 . 7154 . 99951 . 0 www.agosense.com Follow us on... http://www.facebook.de/agosense http://twitter.com/agosense Integration with agosense.symphony HP Quality Center - Atlassian Jira PRODUCT INFORMATION SHEET This product information sheet describes the bidirectional integration between the Hewlett Packard test management system Quality Center/ALM (QC) and the change and defect management system Atlassian Jira (Jira) using the integration platform agosense.symphony. Goal To ensure effective collaboration between developers using Jira and testers using QC, both software tools are linked via the agosense.symphony integration platform using an adapter. The platform makes it possible to synchronise the QC defect management process with Jira and the status update from Jira back to QC with a process that can be individually configured. This means that all necessary details for any defects are available to both parties in close to real time. The Implementation Process Using various modules in the agosense.symphony interface, the processes between the tools are specifically mapped and the attributes to be transferred between QC and Jira are linked in the mapping module. The synchronisation process can be started manually by the user, or the start may be automated. The times or events to trigger the synchronisation process are defined in the scheduling module. The process checks whether the fields for each individual defect can be transferred correctly from QC to Jira, and, using md5 checksum, whether the data has been changed since the last transfer. Only the data that has been changed will be transferred, ensuring a more efficient process. Where an error occurs during the synchronisation, the process is stopped, and the error is documented in the agosense.symphony reporting module. The user can identify the error in the reporting module, and then restart the process. Figure 1 is a schematic representation of the integration between the two software tools. In HP QC/ALM, testers create the required test cases per requirement. Where a test case results in an error, a defect is created in QC. Defects are then transferred to Atlassian Jira via agosense.symphony. Attachments can also be synchronised. Synchronisation processes can also be modelled and configured for automated transfer using the modules in agosense.symphony. Developers working with Jira then process the synchronised defects and change their status as necessary - for example to fixed or incomplete. The changes are then transferred back to HP QC. The Synchronisation Process The following screenshots provide a simple overview of the process between the two tools. Screenshot 1 shows the QC interface with a list of defects that has been created for test cases where an error has occurred. Screenshot 2 shows the reporting module in the symphony interface. All synchronisation processes, both successful and those where errors occurred are documented individually. Screenshot 3 shows the defects list in Jira after successfully synchronisation. Screenshot 4 shows the reverse process - developers working in Jira process the defects and change their status (for demonstration purposes set to fixed). Advantages & Uses Automated bidirectional synchronisation of defects from QC to Jira and of changes in status from Jira back to QC. Transfer of attachments such as pictures, tables, OLE objects etc. Developers and testers both work with only one tool and always have access to all information regarding defects, with automa- ted and regular updates. Effective synchronisation process using checksum Fig. 1: Schematic integration between HP Quality Center/ALM and Atlassian Jira via agosense.symphony Atlassian Jira Defects werden nach Jira synchronisiert, bearbeitet & Statusänderungen zurücktransportiert HP Quality Center/ALM Pro Requirement werden Testfälle angelegt Tests Erzeugt ein Testfall Fehler, werden dafür Defects angelegt Defects agosense.symphony Modellierung der Geschäftsprozesse & automatischer Datentransfer inkl. Anhängen

HP Quality Center - Atlassian Jira - agosense GmbH · HP Quality Center - Atlassian Jira PDUT IFATI SEET This product information sheet describes the bidirectional integration between

  • Upload
    others

  • View
    23

  • Download
    0

Embed Size (px)

Citation preview

Page 1: HP Quality Center - Atlassian Jira - agosense GmbH · HP Quality Center - Atlassian Jira PDUT IFATI SEET This product information sheet describes the bidirectional integration between

1/2HP Quality Center - Atlassian Jira | 2012-06-01

agosense GmbHStammheimer Str. 10 70806 Kornwestheim

[email protected] +49 . 7154 . 99951 . 0www.agosense.com

Follow us on...http://www.facebook.de/agosensehttp://twitter.com/agosense

Integration with agosense.symphony

HP Quality Center - Atlassian Jira

PRODUC T INFORMATION SHEE T

This product information sheet describes the bidirectional integration between the Hewlett Packard test management system Quality Center/ALM (QC) and the change and defect management system Atlassian Jira (Jira) using the integration platform agosense.symphony.

GoalTo ensure effective collaboration between developers using Jira and testers using QC, both software tools are linked via the agosense.symphony integration platform using an adapter. The platform makes it possible to synchronise the QC defect management process with Jira and the status update from Jira back to QC with a process that can be individually configured. This means that all necessary details for any defects are available to both parties in close to real time.

The Implementation ProcessUsing various modules in the agosense.symphony interface, the processes between the tools are specifically mapped and the attributes to be transferred between QC and Jira are linked in the mapping module.

The synchronisation process can be started manually by the user, or the start may be automated. The times or events to trigger the synchronisation process are defined in the scheduling module.

The process checks whether the fields for each individual defect can be transferred correctly from QC to Jira, and, using md5 checksum, whether the data has been changed since the last transfer. Only the data that has been changed will be transferred, ensuring a more efficient process.

Where an error occurs during the synchronisation, the process is stopped, and the error is documented in the agosense.symphony reporting module. The user can identify the error in the reporting module, and then restart the process.

Figure 1 is a schematic representation of the integration between the two software tools. In HP QC/ALM, testers create the required test cases per requirement. Where a test case results in an error, a defect is created in QC. Defects are then transferred to Atlassian Jira via agosense.symphony. Attachments can also be synchronised. Synchronisation processes can also be modelled and configured for automated transfer using the modules in agosense.symphony. Developers working with Jira then process the synchronised defects and change their status as necessary - for example to fixed or incomplete. The changes are then transferred back to HP QC.

The Synchronisation Process The following screenshots provide a simple overview of the process between the two tools.

Screenshot 1 shows the QC interface with a list of defects that has been created for test cases where an error has occurred.

Screenshot 2 shows the reporting module in the symphony interface. All synchronisation processes, both successful and those where errors occurred are documented individually.

Screenshot 3 shows the defects list in Jira after successfully synchronisation.

Screenshot 4 shows the reverse process - developers working in Jira process the defects and change their status (for demonstration purposes set to fixed).

Advantages & Uses

Automated bidirectional synchronisation of defects from QC to Jira and of changes in status from Jira back to QC.

Transfer of attachments such as pictures, tables, OLE objects etc.

Developers and testers both work with only one tool and always have access to all information regarding defects, with automa-ted and regular updates.

Effective synchronisation process using checksum

Fig. 1: Schematic integration between HP Quality Center/ALM and Atlassian Jira via agosense.symphony

Atlassian Jira

Defects werden nach Jira synchronisiert, bearbeitet

& Statusänderungen zurücktransportiert

HP Quality Center/ALM

Pro Requirement werden Testfälle

angelegt

Tests

Erzeugt ein Testfall Fehler, werden dafür

Defects angelegt

Defects

agos

ense

.sym

phon

y

Modellierung der Geschäftsprozesse &

automatischer Datentransfer

inkl. Anhängen

Page 2: HP Quality Center - Atlassian Jira - agosense GmbH · HP Quality Center - Atlassian Jira PDUT IFATI SEET This product information sheet describes the bidirectional integration between

2/2HP Quality Center - Atlassian Jira | 2012-06-01

agosense GmbHStammheimer Str. 10 70806 Kornwestheim

[email protected] +49 . 7154 . 99951 . 0www.agosense.com

Follow us on...http://www.facebook.de/agosensehttp://twitter.com/agosense

Integration with agosense.symphony

HP Quality Center - Atlassian Jira

PRODUC T INFORMATION SHEE T

Screenshot 5 demonstrates how testers using QC are informed about the change in status - initially before the synchronisation via agosense.symphony.

Screenshot 6 shows the QC interface after successful synchronisation via agosense.symphony - with updated defect statuses.

1 2

3 4

5 6