1 week is fascinating. Was it like – the missing piece was modern version control/CD? What kind of testing would need that? (We have configs at work where the system interactions are so unknowable and the financial implications of reduced efficiency so profound that we have to run multi-week A/B tests to change values) Was it some kind of pathological documentation culture?
AFAIR, there were two aspects to testing. The code change itself obviously only took tens of minutes, if that. First round of testing was just the build test, and that was fully automated but I think there were independent builds for multiple different hardware variations and so the total time for that was several days. Then there was actual use-case testing ... I wasn't involved in that at all, but was told it would also take several days of actual testing by a QA team.
