Timeline for The concept of "quality gates" in software testing
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2016 at 19:09 | vote | accept | Nelfo | ||
| Mar 14, 2016 at 21:54 | comment | added | Nelfo | The main argument the proponent of these gates for functional tests seems to be that if multiple teams are working on multiple interdependent components of an application, we can't hold up deployment of a component to a staging environment until all its tests pass, because that would hold up other teams' integration with our component. So each environment has a tighter gate until finally production is 100%. I don't know if letting other teams integrate with a component that is 30% broken is the best way to achieve this. | |
| Mar 14, 2016 at 17:55 | history | answered | amon | CC BY-SA 3.0 |