Get in touch

Engioscope in Action

A case study - Data-driven Coaching

Time spent - Finished Features

Where did the features that finished in the last 90 days spend their time?

Flow Efficiency

Fraction of overall time that work items spend in work centers on average

Work in Progress Trend

Trend of work items in progress per day over the last 90 days

Bug Leakage with root cause

Bugs leaked over the last 90 days with their root cause

Why are we finding these issues so late in the game?

Let's understand what was happening? The following are the issues we discovered even though the team thought everything was under control

    OpenAPI Specification / Swagger Sync Issues

    Even though there is a Cl step to generate and push the latest OpenAPI Specification/Swagger file in dev portal, in some cases, it was out of sync.

    Contract Tests Failing

    Even though OpenAPI Specification / Swagger  is generated from code using CodeGen, when we ran contract tests against the code, it would fail.

    Delayed Consumer Testing

    Consumers would have done development using request/response pairs, hoping that they would get the service in the dev environment to test before the release, but often that would come very late, and real testing would happen in SIT.

    API Design Evolution Gaps

    Between design and development, as more knowledge and constraints are revealed, the API schema and design would evolve, but the same would not be captured and communicated explicitly to the Architect and Consumers.

    Backward Compatibility Breaks

    While updating existing APIs, the changes would break backward compatibility - but would only identify this during regression testing with an older version of the consumer.

    Test Data Management Challenges

    Test data management across 100s of systems was extremely difficult.

    External Dependency Testing Gaps

    External dependencies (payment gateways, service subscription integration) were not available for testing.

    Performance and Chaos Testing Issues

    Perf testing and chaos testing in the Staging environment would surface issues with back-pressure (circuit breaker) or empty state and error state handling.