This "why" could go in many different ways other than testing depending on the question you ask and the rigor you apply.
"
Why was the integration code only set up for 20 inputs?
Because the new IPC Template Type, introduced in February 2024, defined 21 input fields, but the testing processes did not include a scenario where the 21st input field was required.
"
Strictly speaking, the respomse to the specific question shouldn't really talk about testing. Next question would be "why did it define 21 fields". Perhaps a question like "why was this breaking change allowed to make its way into prodiction?" would reveal the issue with the test much sooner.
We do need branches of whys that focus on different aspects.
With CrowdStruck, we have several roots to start with:
root 1: why was this able to make it into prod undetecred?
root 2: why did it take so long to recover?
root 3: why did the breaking change exist in the first place?
And perhaps different groups would ask different questions depending on their context.
Microsoft might ask their own questions..
root 1: why was a vendor defect able to cause our severe service outage?
Ask the right questions starting in different contexts and stick to those contexts to get the most benefit.
This "why" could go in many different ways other than testing depending on the question you ask and the rigor you apply.
"
Why was the integration code only set up for 20 inputs?
Because the new IPC Template Type, introduced in February 2024, defined 21 input fields, but the testing processes did not include a scenario where the 21st input field was required.
"
Strictly speaking, the respomse to the specific question shouldn't really talk about testing. Next question would be "why did it define 21 fields". Perhaps a question like "why was this breaking change allowed to make its way into prodiction?" would reveal the issue with the test much sooner.
We do need branches of whys that focus on different aspects.
With CrowdStruck, we have several roots to start with:
root 1: why was this able to make it into prod undetecred?
root 2: why did it take so long to recover?
root 3: why did the breaking change exist in the first place?
And perhaps different groups would ask different questions depending on their context.
Microsoft might ask their own questions..
root 1: why was a vendor defect able to cause our severe service outage?
Ask the right questions starting in different contexts and stick to those contexts to get the most benefit.