Harmonize Pro LogoHarmonize Pro

QA & Testing Workflows

Organize your testing process with nested checklists, automated test execution tracking, and seamless bug triage workflows.

Test Case Execution Inside Story Ticket

Execute comprehensive test cases directly within the story ticket, eliminating the need for separate test management tools.

Workflow Structure:

  1. Nested Exploratory Testing Checklist
    • Smoke tests
    • Functional tests
    • Regression tests
    • Performance tests
  2. Attach File Items - Required uploads for screenshots, videos, and logs
    • Screenshot of test results
    • Video recording of bug reproduction
    • Log files from test execution
  3. Blocker Between Test Groups - Ensures proper sequencing (smoke → functional → regression → performance)
  4. Final Notify Trigger - Sends "All tests passed" with green badge to Teams + auto-moves issue to "Ready for Release"

✅ Advantage: All test evidence and results live in one place, creating a complete audit trail.

Bug Triage Directly in Original Story

When testers find bugs, convert them to separate issues without losing context or breaking the workflow.

Workflow Structure:

  1. Testing Checklist Item - Tester identifies a bug during test execution
  2. Convert to Separate Issue - Click on the checklist item to convert it
    • Creates linked bug issue automatically
    • Auto-assigns back to original developer
    • Preserves context and test evidence
  3. Blocker Added Automatically - Main story can't be closed until the new bug is resolved
  4. Notify Trigger - Alerts developer about the new bug issue
  5. When Bug is Fixed - Blocker is cleared and testing can continue

🔗 Context Preservation: Bugs stay linked to their original test case, making it easy to track what was tested and what failed.

Structured Test Phases with Blockers

Organize testing into distinct phases, each gated by blockers to ensure proper sequencing.

Phase Structure:

Phase 1: Smoke Tests

  • Basic functionality checks
  • Critical path validation

→ Blocker unlocks Phase 2

Phase 2: Functional Tests

  • Feature-specific test cases
  • Edge case validation

→ Blocker unlocks Phase 3

Phase 3: Regression Tests

  • Full regression suite
  • Integration tests

→ Blocker unlocks Phase 4

Phase 4: Performance Tests

  • Load testing
  • Stress testing
  • Performance benchmarks

Automated Test Evidence Collection

Use attach file items to ensure all required test evidence is collected before marking tests as complete.

Required Attachments:

  • Screenshots - Visual proof of test execution and results
  • Video Recordings - For complex interactions or bug reproduction
  • Log Files - System logs, error logs, and test execution logs
  • Test Reports - Automated test results from CI/CD pipelines
  • Performance Metrics - Response times, throughput, resource usage

Best Practices

  • Use blockers between test phases to ensure proper sequencing and prevent skipping critical tests
  • Always require file attachments for test evidence to maintain audit trails
  • Convert bugs to separate issues immediately to maintain traceability
  • Use notify triggers to keep stakeholders informed of test progress and results
  • Structure test checklists hierarchically to match your test organization (smoke → functional → regression)
  • Leverage change assignee triggers to rotate testing work across team members