FYI: The code I wrote for Selenium Testing of extensions takes screenshots and plays them in a slideshow for you after the testing is completed.
I did this so it would be possible to inspect layouts. My code has not been committed to core yet. On Mon, Sep 19, 2011 at 11:39 AM, Trevor Parscal <[email protected]>wrote: > I've been aware of this tool for quite a while, and shown it to some other > devs around here. I think it's awesome, but I have not had a need for it > yet. I think the visual editor may present some cases where this makes > sense > - but generally it seems the most useful for writing tests that involved > taking several input actions and expecting a consistent result. Imagine how > useless this may be with testing that searing for something in Google > returns a search result - the results change constantly, how would you test > that? I think it's a cool tool, and we should consider it when testing, but > not go out of our way to use it. > > - Trevor > > On Mon, Sep 19, 2011 at 7:30 AM, Markus Glaser <[email protected]> > wrote: > > > Hi, > > > > while I don't like the idea of introducing more and more testing tools, I > > can still see an interesting use case here: as of now, we have no way to > > test whether a given layout (HTML, JS, CSS) is really rendered the way we > > want it to be, since both Selenium and QUnit make their tests based on > DOM, > > right? Sikuli on the other hand seems to be based on screenshots and here > we > > could detect broken layout. There is also some kind of similarity > algorithm > > (which I hope is configurable) so that one test could be used in > different > > browsers even if the rendering is not identical to the pixel. > > > > The question is, do we have the need for testing screen layout? > > > > Cheers, > > > > Markus > > > > P.S.: CCing wikitech, since this might be of broader interest. > > > > > > -----Ursprüngliche Nachricht----- > > Von: Sumana Harihareswara [mailto:[email protected]] > > Gesendet: Dienstag, 30. August 2011 14:02 > > An: Markus Glaser; Chad Horohoe; Timo Tijhof > > Betreff: automated testing with Sikuli? > > > > http://sikuli.org/ > > > > Have any of you run across Sikuli before? Just wanted to point it out to > > you. It might face the same problems as Selenium, though. > > > > -- > > Sumana Harihareswara > > Volunteer Development Coordinator > > Wikimedia Foundation > > > > _______________________________________________ > > Wikitech-l mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Jeremy Postlethwaite [email protected] 515-839-6885 x6790 Backend Software Developer Wikimedia Foundation <http://wikimediafoundation.org/> _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
