[Bug 29727] [xslt30ts] aspiring-001


--- Comment #3 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
(In reply to Michael Kay from comment #2)
> The trouble generally with more complex tests is that debugging real or
> imagined test failures can be an awful lot of work. (For example, the test
> framework for system-property() is so complex that if one test gives the
> wrong result, isolating the reason can be a nightmare.)
While I agree, they also showcase the ability of the spec staying solid and
yielding processor-independent and equal results for less-than the most trivial
or even non-trivial but isolated cases.

I created this category for tests that are reported "from the wild", and are
often not fit for a single category.

Furthermore, implementations failing a more complex test can either decide not
to run it, challenge the test, or, if it is a bug in the implementation, fix it

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 5 November 2016 11:06:22 UTC