Developer-Tester Alignment

It’s often said that there exists a cultural divide between developers and testers. But one thing that brings them together is the need to identify and remediate defects. Unfortunately, the fact that testing teams use test and defect management tools, while the developers prefer to find their work assignments in issue trackers or Agile planning tools, continues to perpetuate the divide between testers and developers.

For example, testers may use a test management tool (such as HPE QC) to manage their testing and the resulting defects. But the developers may prefer to track these defects as issues in an issue tracking tool (such as Atlassian JIRA or Targetprocess). With the “Developer-Tester Alignment” (formerly known as “Defect Unification”) integration pattern in place, whenever a defect is created in HPE QC, that defect is mirrored in JIRA as an issue. The developer finds all the information they need in JIRA and updates the JIRA issue when they have fixed the bug. The information from that JIRA issue is immediately synched back to HPE QC and the tester can see that the bug has been fixed and is ready for retest.

Because the alignment between testers and developers is such a critical issue in the software development process, this integration pattern is the most common pattern we see.

Developer-Tester Alignment

Artifacts typically synchronized:

  • Defects/Bugs
  • Issues