Paul Kienzle wrote: > On Thu, Sep 06, 2007 at 08:14:19AM -0400, Michael Droettboom wrote: >> On a broader note, I've been using backend_driver.py as my ersatz >> "acceptance test suite." Not all of these examples are included in it, >> of course. Is there good reason for that, or should I go ahead and add >> these to backend_driver? As we're all well aware, matplotlib has an >> unusually large configuration space, so any bit of testing automation >> really helps. > > We could store a copy of the png output somewhere in the svn tree. Then, > whenever we change something we can do a binary comparison on all the > plots. It would avoid issues such as breakage of polar plots where the > author of the changes didn't consider that it would affect polar plot > output. Similarly for ps/pdf. Differences in fonts between platforms > might be a problem in this scheme.
We could have a special flag for font_manager.py that only loads fonts from mpl-data/fonts. Then the results for Agg should theoretically be the same across platforms. The Gdk, Cairo and wxRenderer would all have slightly different results across platforms, however, as the underlying font engines could change. Alternatively, we could sidestep this problem by producing a set of PNG images for each platform which would have to be individually verified on a per-platform basis. It (at least) triples the verification work, but cuts down on work in other areas... Cheers, Mike ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
