Signadot Blog
-
Shift Left on a Budget: Cost-Savvy Testing for Microservices
Why extra environments and more brittle E2E tests do not fix slow releases, and how lightweight preview environments in one shared environment let developers run E2E tests before merge.
-
Integration/E2E TestingIs The Testing Pyramid Broken?
Why unit, integration and end-to-end tests each fall short in microservice architectures, and what a fix requires: decentralized testing before merge in a production-like environment.
-
Integration/E2E TestingHow to Test Event-Driven Architectures Without Duplicating Infrastructure
A model for testing event-driven systems on one shared baseline: carry a routing key in every message, let consumers choose what to process, and apply it to pub/sub, CDC and batch flows.
-
Integration/E2E TestingTesting Event-Driven Architectures with OpenTelemetry
Three ways to test Kafka workflows (isolated infrastructure, isolated topics, isolated messages on a shared queue), and how to build message isolation with OpenTelemetry context propagation.
-
Ephemeral EnvironmentsMultitenancy Is Fundamental to Shift-Left Testing
Why fast tests and accurate tests are a false choice, why copying staging clusters fails, and how a multitenant shared cluster, as at Uber and DoorDash, brings accurate tests earlier.
-
Integration/E2E TestingWho Should Run Tests? On the Future of QA
As testing shifts left, QA should not get code developers have not tested. Why QA stays valuable, and how QA embedded in product teams owns testability, regressions and service interactions.
-
Ephemeral EnvironmentsShifting Testing Left: Isolating Changes on a Shared Cluster
How isolating each change lets many developers test on one reliable shared cluster, the request routing and context propagation it needs, and how Uber's SLATE and DoorDash do it.
-
Integration/E2E TestingHow to Shift Testing Left: 4 Tactical Models
Four ways teams shift testing left for microservices (developer-owned integration and contract tests, feature flags, on-demand environments and post-merge tests) and where each falls short.
-
Integration/E2E TestingWhy Shift Testing Left Part 2: QA Does More After Devs Run Tests
When developers run their own tests, QA does more, not less: setting test strategy, owning automation frameworks and working inside product teams, much as sysadmins moved on from email servers.
-
Integration/E2E TestingWhy We Shift Testing Left: A Software Dev Cycle That Doesn’t Scale
Why testing after development stops scaling as a company grows, why hiring more QA does not fix it, and how shifting integration and end-to-end tests to developers restores a faster loop.
-
How to Understand and Improve Your Developer Experience
How to find out what your developers' experience really is, through a holistic view and regular audits, then improve it by protecting flow, building connection and speeding up feedback.
-
Are you Delivering on Developer Experience?
Three ways poor developer experience holds teams back: developers rarely reach flow, collaboration suffers and feedback is low quality. Surveys of developer sentiment make it visible.
No matching posts found.
Stay in the loop
Get the latest updates from Signadot