I guess applications living in the browser don't align well with Apple's interest in pushing their app store.
There actually are some partial tests from the W3C regarding basic web technologies, but they're not really automated ones in the way you'd think.
I only mean to say that you don't need a whole compliance testing suite to catch a major bug like this.
Its not really a test suite, but back in the early days of CSS we had https://en.m.wikipedia.org/wiki/Acid2 It'd be easy to write a set of tests based on Acid2.
There's also https://en.m.wikipedia.org/wiki/Acid3 but that doesn't quite test things 'properly'.
In addition the specs have changed somewhat so now CSS 2.1 and the modules that existed at that point in time have matured beyond what the tests were written for, so a browser matching the spec today would fail.
They were very fun for end users to see whether or not a browser was in compliance, though!
Such an effort would probably involve a higher level of ongoing support from the vendor side of the fence (in terms of motivation and iterative discussion etc), but relative to other options might be, as I said, the path of least resistance.
</armchair_idea>
However, if you do stumble on some tests for basic things like the box model, I'd love to know where they are! Tests like those would allow other vendors to know whether or not they're adhering to specification, programmatically.
Earlier standards are very descriptive, rather than telling you how to implement the actual web technologies. That's left as an exercise for the reader. Seriously!