Microsoft’s Evolution of Software Testing: From 1990s SDET/STE Model to Combined Engineering in the Cloud Era

1. 1990s: How Microsoft Tested

Microsoft historically allocated three core roles per product team: Product Manager, Developer, and Tester, with a staffing ratio of roughly 0.5 : 1 : 1. Testers were split into Software Design Engineer in Test (SDET), building test infrastructure and automation, and Software Test Engineer (STE), executing tests.

a) How It Operated

The model succeeded for large products like Windows and Office, relying on formal quality metrics and acceptance criteria. Test teams amassed deep expertise, but the process became a bottleneck as development handed code to SDETs, who passed automated tests to STEs, leading to costly staffing and delayed releases.

b) What Failed

By the late 1990s the approach proved ineffective: STEs faced limited career growth, high costs, and testing became a release blocker, exposing the model’s flaws despite commercial success.

2. First Transformation (circa 2000): Merging SDET and STE

Microsoft eliminated the STE role, requiring SDETs to both create and run automated tests. This shift improved ownership but SDETs still struggled to keep pace with new feature development, prompting the introduction of a “Quality Milestone” (MQ) phase to address test debt, which ultimately proved counter‑productive.

3. Fast‑Paced Internet Era

The rise of cloud services demanded faster delivery and continuous deployment, rendering the long‑standing stability phase obsolete. Traditional beta or “dogfood” validation no longer sufficed, and micro‑services required high availability and zero‑downtime deployments.

Microsoft initially tried to accelerate existing automation, executing only tests impacted by code changes, but this proved insufficient as testing became the primary bottleneck, consuming entire iteration cycles.

4. Changes in Quality Assurance for the Cloud Era

Recognizing the inadequacy of the old model, Microsoft redefined software quality responsibility, emphasized keeping the Master branch always release‑ready, and shifted testing left (more unit tests) and right (quality checks closer to production).

5. Organizational Shift of Quality Responsibility

Microsoft introduced “combined engineering,” merging development and testing into a single “engineer” role that encompasses both SDE and SDET skills. This required extensive cross‑training: developers learned testing, testers learned coding, and managers learned end‑to‑end feature delivery.

The new model eliminated hand‑offs, making each engineer accountable for the full quality lifecycle—from unit to performance testing, deployment, and monitoring—while fostering peer reviews and shared responsibility.

6. How the Transformation Was Executed

The transition was carefully planned over about 12 months, inventorying all testing activities and redefining them within the combined role. Engineers gradually acquired new skills through iterative learning, eventually blurring the distinction between SDE and SDET.

7. Addressing Specialized Concerns (Performance, Security, etc.)

Specialized “virtual teams” were formed to retain expertise in areas like performance testing and security while embedding these specialists within feature teams, ensuring both depth of knowledge and end‑to‑end ownership.

8. Achieving Higher Delivery Speed

Although individual engineers took on more responsibilities, the elimination of hand‑offs and the adoption of new testing practices led to a noticeable increase in feature delivery speed and overall productivity.