A classic example of crummy software testing
Microsoft unleashes a poorly tested version of
windows media player on the macintosh audience
I have to put in a little disclaimer here. I
worked on the Windows Media Team for (PC) version
7.
That said, tonight I tried to
install the newest version for the macintosh, version 9 onto one of my macs. I
installed it through a non-admin account (I didn't want it in my account), it
seemed to install ok, except that it didn't give me an option of where to put it
and it demanded the admin password. When I try to run it from this account, I
get a "you do not have privileges to run this application" error. I switch to my
admin. All the ownership and execute attributes on the application are fine. I
can run it from my admin account just fine (remember that I didn't even want to
be accessible from any other account), but in this lower permission account I
can't run it. Even though that is the account I installed it
from.
Now this is, of course, a bug. A
bug I have caused myself in the recent past. It is also a very easy bug to fix
and a very easy bug to find if you are testing your product. It is testing 101
and one of the first things a good tester will catch. An important note is that
the WMP for mac wasn't developed in the Mac BU during my time in Windows Media,
it was part of the Windows Media Team. This might explain why the quality might
not be up to the Mac Office standards. MSN suffers from this problem too, I've
heard.
Bugs get through, it happens.
There is no excuse for something this obvious to get through the cracks though.
Especially in a politically sensitive area for Microsoft like this. Microsoft
needs to improve their quality on non-windows platform for their media player if
they expect it to be any sort of real web standards. Until their quality gets
better, I'm going to bug the websites I view to embrace a real cross platform
video format like Flash, or Quicktime.
Posted: Tue - June 21, 2005 at 10:54 PM
|
