On Feb 26, 2012, at 16:19, Ryan Schmidt wrote: > On Feb 26, 2012, at 15:17, Tauren Mills wrote: > >> The reason I mentioned Buster.JS is that it will help you to automate >> running your tests across multiple browsers. It sounded like your testing >> process was going to be manually intensive, and it could simplify it. You >> can set up a buster server and attach *real* browsers to the server, >> including Chrome/Safari/FF/IE/IOS/Android/etc. Then when you run your tests, >> it will run them simultaneously on all attached browsers and report back >> success or failure for each. I didn't suggest it because it had any features >> specifically related to graphics, but that it might simplify your testing >> process. Other similar tools include jsTestDriver and TestSwarm. > > Oh that does sound useful, and I didn't understand that from my quick reading > of their page, so thanks for pointing that out.
The hour-long presentation video at the centerpiece of the http://busterjs.org/ homepage was helpful in explaining how to get into testing in general, and how buster.js works in particular; I'd recommend it, especially the first 15 minutes of it, to anyone not sure how to start with testing. I think I'm going to use buster.js for now, and write my own custom image comparison method which my tests will use. That should work well enough for passing tests. I'm not sure yet how I'll handle failing tests; ideally I'd like to see the reference graphic, the actual graphic, and a difference between them, but buster's test output is just text. On Feb 26, 2012, at 19:20, Shimon Doodkin wrote: > maybe http://sikuli.org Thanks for the suggestion. I'm familiar with Sikuli, and it's not so much a testing environment, as a graphical scripting language. It doesn't answer the question I had: how to compare two graphics and decide if they're sufficiently similar and maybe show the differences. It answers the question: given a GUI that does not have a proper scripting interface, how do you automatically control it? It lets you write scripts that say things like "Wait until a button that looks like this screenshot appears, then click it." It's an interesting project but I don't think it's applicable to my problem. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
