To pick back up on this thread, I was looking at the FXL tests and find
myself agreeing with what Ric has noted in his comments. I was going to take a
stab at some clean up the descriptions and success criteria, but also noticed
along the way that they aren’t atomic tests, but are coupling two behaviours
(e.g., most of the test require checking that there is no fault with the
orientation and no fault with synthetic spreads being generated to pass, but
either could fail independently of the other).
I’m still okay with doing some editorial work, but I was wondering whether
we need to keep all these permutations in the test suite? Wouldn’t it be simpler
to test all the global values of rendition:orientation leaving rendition:spread
set to auto and then test all the values of rendition:spread leaving
rendition:orientation set to auto? We could drop a third of the combinatory
tests that way and get the same support information.
At least in my mind (which is known to be buggy), if one or the other
global setting fails in isolation, it will fail in combination with any other
global value, and the we’re not out to test how ugly something might look (e.g.,
forcing all pages into landscape mode in a synthetic spread when the device is
held in portrait mode to see how tiny the pages come out).
As it is now, if we keep the current set up, but split the testing within
each publication for each global value, we end up testing the same functionality
repeatedly.
Matt