Some of the code will be very old and from the time before such practices were really practicale let alone established: back in the day it either worked or it didn't.
However, things really weren't helped when Microsoft sacked its entire testing team. It didn't integrate into the relevant development teams or change the process, it just sacked them because it was the easiest way to lower the headcount and juice the numbers at the time. It hasn't really recovered since then.
Google rightly takes a lot of flak for some of its decisions – though withdrawing free services doesn't really count – but it has for a long time had clear (if a bit weird) coding practices, including testing and dedicated security team that actually looks for bugs. That's why we do read about the occasional SNAFU in deployment, but also see Chromium bugs fixed very quickly. I'd argue that much of this stems from the fact the Google uses a lot of open source software and even employs developers to maintain open source projects, where testing has long been standard as has gratefully accepting good bug reports. Yes, Chrome does do a lot of tracking, but the underlying Chromium is there for those that care.
Fundamentally, Microsoft hasn't changed in how it sees customers and, therefore, how it develops software: embrace, extend, extinguish still seems to be the strategy, with extinguish also applying to any kind of quality assurance. And, as long as people are happy to use Edge as a browser, who can really blame them?