On 1 June 2006 at 14:19, Chris Gray <[EMAIL PROTECTED]> wrote: > I believe that Classpath uses the VisualTestEngine we developed at Acunia. > Requires manual operation, but it has facilities for explanatory texts, pass/ > fail indications, etc.. It will even run applets if you ask it nicely. You > can find it in the SVN repository at www.wonka-vm.org (which is down at the > moment I write this, I'll ping Luminis to ask why). > > I don't think it's that difficult to hack X to write to normal RAM > instead of a framebuffer, but the real problem is that there's no hard > spec of which pixels should change to what colour when you create e.g. > a button. You could instrument an X server in other ways though, for > example to see that [J]Frame actually opens a new window and sets its > title.
I don't think you even need to hack X. Simplest way to do a perfect comparison that springs to mind is: 1) Start an X virtual framebuffer on display :1, with: Xvfb :1 & 2) run RI test, using DISPLAY=:1, periodically taking snapshots[0] with: xwd -display :1 -root -out NN.xwd 3) repeat the tests with harmony 4) compare the resulting *.xwd files The hard part would be to elaborate on step 4 to support minor variations in the comparison process. If you were comparing manual/visually, ImageMagick does quite a good job with: compare ri.xwd hy.xwd :x If I recall correctly difference tend to be shown in bright red. Regards, Mark [0] I mean instrument the tests with calls to do this. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
