Microsoft notoriously fired all their QA engineers back in 2014. I would assume that QA is no longer a core competency at Microsoft. I'm guessing that they have testing tasks that are now performed by contractors, but no actual _process_ in place to assure quality. The only engineering process now is agile.
My experience as a QA engineer testing software in agile environments in the last 15 years or so is that my attention every sprint is focused first on assuring that the features implement the user stories, and second that the automated regression tests are written and checked into version control. This automation task is where the majority of my 80 hours every sprint is spent. There is no time to check for bugs by way of, say, ad-hoc testing.
If I'm a contractor, all the buttons are on the screen, and the only issue is that the buttons aren't centered, then I'll enter a bug for the alignment issue as a low priority fix and clear the feature to ship. I might POSSIBLY perhaps maybe add a note to the bug suggesting a workaround by sending an InvalidateRect message to the window containing the buttons, but I doubt it knowing that the developer outside of the team would never read it.
I will absolutely NOT be an advocate for the developer experience and refuse to clear the feature to ship with this bug knowing how tenuous my employment status is, however. I would guess that that's how this bug passes QA in the first place.
Microsoft notoriously fired all their QA engineers back in 2014. I would assume that QA is no longer a core competency at Microsoft. I'm guessing that they have testing tasks that are now performed by contractors, but no actual _process_ in place to assure quality. The only engineering process now is agile.
My experience as a QA engineer testing software in agile environments in the last 15 years or so is that my attention every sprint is focused first on assuring that the features implement the user stories, and second that the automated regression tests are written and checked into version control. This automation task is where the majority of my 80 hours every sprint is spent. There is no time to check for bugs by way of, say, ad-hoc testing.
If I'm a contractor, all the buttons are on the screen, and the only issue is that the buttons aren't centered, then I'll enter a bug for the alignment issue as a low priority fix and clear the feature to ship. I might POSSIBLY perhaps maybe add a note to the bug suggesting a workaround by sending an InvalidateRect message to the window containing the buttons, but I doubt it knowing that the developer outside of the team would never read it.
I will absolutely NOT be an advocate for the developer experience and refuse to clear the feature to ship with this bug knowing how tenuous my employment status is, however. I would guess that that's how this bug passes QA in the first place.
Edit: Clarified a few statements.