3 ms·
Well, you can't really blame QA all that much. This would have only been caught if the QA team decided to turn the clock forward a few days just to see what wo
by dmackdaddy 18y ago
Well, you can't really blame QA all that much. This would have only been caught if the QA team decided to turn the clock forward a few days just to see what would happen. This was the Developer's fault for not checking the code for expiration on a BETA. Glad we waited to Update to U2 tho!
- gojomo 18y agoSure, you can blame their QA. QA for such a big company, with calendar-sensitive products, should be running full acceptance tests at a number of dates in the future. Malware researchers do this with honeypot machines to see if certain actions are triggered at upcoming dates. VMWare should be doing this even if for no other reason than to verify that their intended license-expiration works as expected.
- Kaizyn 18y agoBig corporations that have software everyone wants to use can treat their paying customers as beta testers. You know this drill as Microsoft pioneered the practice a long long time ago.
- stcredzero 18y agoBig corporations also treat their production staff using in-house software as beta testers, even if this costs them many millions of dollars in the few days after each release. (Because hiring a test staff for less than a million would be "too expensive.") It says a lot when a company can treat customers in the general public like in-house employees it can abuse.