A common problem when writing recipes is that many steps output JSON data, but when the test didn't supply it, the returned days details to some possibly-fine value like None. This data ends up percolating down the recipe until it ends up breaking some other assumption later.
I think we can improve the experience by having unmocked Placeholders return a special Unmocked singleton, which will cause the recipe engine to raise an exception any time this value is accessed that includes a detailed breakdown of what happened, e.g. Step "somestep" uses an output Placeholder `json.output` which was not mocked in the test.
A common problem when writing recipes is that many steps output JSON data, but when the test didn't supply it, the returned data defaults to some possibly-fine value like None. This data ends up percolating down the recipe until it ends up breaking some other assumption later.
I think we can improve the experience by having unmocked Placeholders return a special Unmocked singleton, which will cause the recipe engine to raise an exception any time this value is accessed that includes a detailed breakdown of what happened, e.g. Step "somestep" uses an output Placeholder `json.output` which was not mocked in the test.
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by aga...@chromium.org
, Apr 26 2016Labels: -Infra-Recipes