Back in my medical software development days, we spent quite a bit of time developing and evolving "test plans." These were a written testing procedure we would use with every update, specifying a series of actions we would do to be sure that each update not only did what it was supposed to do, but didn't break anything else. Based on my own experience and perusing the sequence of issues people repeatedly have with many of the X automated features, the company is failing to do this adequately. It seems that almost every time one problem is fixed, another function becomes broken. Classic "whack a mole." Case in point is the behavior of the easy entry to rear seats. I've had it work perfectly at times but with various updates it breaks again, and breaks in some unique new way! I'd rather have less frequent updates and more testing of each. The problem is that as software matures, it often becomes more complex, and a rigorous test plan becomes that much more critical. That said, this seems to have impact on doors and seats and other peripheral functions. The core of the car, the drive train, autopilot, etc, has been rock solid. Maybe the door/seat team should spend a little more time with the autopilot team.