I haven't looked at this very closely but it sounds like a very high
maintenance way of doing testing. Every time I've built user interface
tests that relied on what things look like the maintenance cost has
been too high to sustain them. Essentially, minor code tweaks results
in hours of updating test cases. I imagine with this method that would
include creating new screen shots that are being compared against. I'm
wary of writing tests that compare against static images.
Michelle
Quoting Jacob Farber <[email protected]>:
Has anyone ever done automated testing for CSS before? If so, have you heard
of http://github.com/garethr/css-test/tree/master or comparing a rendered
webpage image to an master image? I would be interested to hear about any
experiences you may have had with this technique.
Thanks
Jacob
--
Jacob Farber
University of Toronto - ATRC
Tel: (416) 946-3002
www.fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
