Skip to main content
    DevOps
    Way of Working
    1. Home
    2. Capabilities
    3. Test Integration

    Integration Testing

    Foundation
    Phase: test
    CFR
    LT

    Quick Reference

    Phase
    test
    Epic
    Testing Strategy & Quality Gates
    Milestone
    Foundation
    Target
    >= 60% services have integration tests
    Implementation Time
    Part of Testing Strategy & Quality Gates epic: 3 weeks (22 hours per capability avg)

    What & Why

    Definition

    >= 60% of services have integration tests covering critical API endpoints and database interactions.

    Business Value

    Catches 70% of bugs before production deployment and reduces QA cycle time by 50% through comprehensive automated test coverage Achieving >= 60% services have integration tests is a key milestone toward this goal.

    Context

    This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting CFR, LT improvements.

    Success Criteria

    Target

    >= 60% services have integration tests

    Measurement

    Integration test suite analysis per service

    Evidence

    • Integration test code
    • Test reports
    • API contract coverage

    In Practice

    Real-World Implementation

    Teams write integration tests using testcontainers or docker-compose, run in CI, test real DB queries and external API calls.

    Concrete Example

    Service 'order-api' has 15 integration tests: POST /orders (DB insert), GET /orders/:id (DB query), DELETE /orders/:id (cascade delete).

    Implementation Guide

    Prerequisites

    Code Coverage Baseline
    >= 70% branch coverage

    Implementation Steps

    Follow the measurement approach: Integration test suite analysis per service

    For detailed step-by-step guidance, refer to the Testing Strategy & Quality Gates Implementation Kit.

    Resources

    Implementation Kit

    Testing Strategy & Quality Gates Kit

    Templates

    Browse all templates

    Related Resources

    View learning paths

    Related Capabilities

    Prerequisites

    Implement these first

    Code Coverage Baseline

    Enables

    What this unlocks

    Contract Testing Between Services
    Performance Testing in CI

    Complementary

    Often adopted together, from the Testing Strategy & Quality Gates epic

    End-to-End Testing
    Test Data Management
    Flaky Test Detection
    Parallel Test Execution

    Troubleshooting & FAQs

    Common Issues

    Issue: Target metric not improving

    Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness

    Issue: Team resistance to adoption

    Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition

    Issue: Inconsistent implementation across teams

    Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards

    Frequently Asked Questions

    Can we implement this before completing prerequisites?

    While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.

    How long does implementation typically take?

    Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.

    DevOps
    Way of Working

    DevOps practices for the entire delivery lifecycle

    © 2019-2026 devopswow.com. Created by Burhan Öcüt

    PartnersAboutPrivacyTermsCookies