Somehow I find it hard to trust Microsoft to provide a fair test - they have a vested interest in having IE "win". I wouldn't trust a test from Mozilla foundation or Opera either.
While I doubt the tests are explicitly include any kind of favoritism (e.g., "if (browser=IE) GiveAHighScore(); else GiveALowScore();"), you're probably right in that the tests are chosen to showcase things that IE does well. A car company that sells dragsters wouldn't present prospective buyers with a twisty road course on which to test them
I still wouldn't outright dismiss the tests, though--if nothing else, they show that there are some things that IE does better than the competition (or, at the very least, is competitive), and they're not just obscure features that no one's ever heard of--they're "cool" things that you can actually see.
The question is: Since Microsoft has more resources than every other browser producer out there combined, why is it so far behind on standards compatibility? Considering IE has been around longer than Firefox, Opera, and Chrome it should be AHEAD of the curve - not behind.
Well, not everyone at Microsoft works on IE--I imagine a more fair comparison would be just looking at the number of people who actually work on IE.
As for why it's behind, not ahead...the simple reason is that Microsoft is extremely slow to react to change. With Internet Explorer 6 in 2001, Microsoft basically felt the browser wars were over, and IE had won. At the time, Netscape was pretty much dead[
source], Firefox didn't even really exist yet, and Opera had all of .13% of the market share[
source]. Netscape usage declined rapidly, and IE usage was above 90% by the end of 2001, reaching 95% by 2004. Microsoft basically mothballed IE and moved resources elsewhere--if there's no competition, what's the point in spending a ton of resource on it? (No, I don't necessarily agree with that attitude).
Then, in 2004, Firefox started skyrocketing in popularity, and Microsoft had to start up working on IE again, but it took until 2006 for anything new to come out, and IE7 was mainly some UI improvements over IE6 without a great deal of improvements in the Trident engine--basically a stopgap measure. It took another three years after that for IE8, a browser that was actually a real improvement.
The same kind of problem happened in the mobile space--Windows Mobile was doing okay, and then rapidly fell behind as competitors showed up with great new innovations and ideas. Microsoft is again closing the gap with Windows Phone 7, but it's dangerously late to a game that already has quite a few strong players, and still doesn't have feature parity with its competition.
Yes, Microsoft has more resources--but the downside of this is the lack of agility. Microsoft is a very large machine, and it has proven many times that it doesn't have the ability to react quickly to changes in the market.
In the case of IE, the "standards compliance" push was championed by other people first, and IE took a long time to get back into the game.
Is it the best way to run a company? Probably not, but it's the explanation for why IE is behind currently.
There's also seems to be a lot more emphasis on not breaking things, given the much slower ship cycle that IE has compared to the other browsers--if Firefox breaks some webpages when it releases a version, oh well, the next version will be out before too long. The same can't be said for IE. This translates into a whole lot more time spent by developers and testers in making sure that old things don't break while you're adding new features.