Ryan, Sorry if I wasn't clear, but I didn't really expect either of my suggestions to solve your testing needs. Rather, I just wanted to make sure you were aware of them, because you might be able to find a way to leverage one or both as part of a solution to your problem.
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. I realize PhantomJS will not help you test every browser but thought it might be good enough to cover 90% of your needs and you could resort to other more manual methods for the remainder. In fact, I haven't really used PhantomJS at all except to try out the render script. Since I do not yet know what all it is capable of, I thought that it might potentially be useful to you. I'd certainly like to hear about whatever solutions you do come up with. Best of luck! Tauren On Sat, Feb 25, 2012 at 5:57 PM, Ryan Schmidt <google-2...@ryandesign.com>wrote: > > On Feb 25, 2012, at 18:35, Tauren Mills wrote: > > > I don't have an out-of-the-box solution for you, but if I was in your > shoes I'd be looking into Buster.JS and Phantom.JS to see if they could > help: > > Thank you for your response. I had not heard of these projects before. > > > > http://busterjs.org/ > > This seems to be a normal testing framework, much like any of the dozens > of other testing frameworks I've heard mentioned on this list before. If > you believe it has specific graphics-related capabilities, please point me > to them, otherwise I'm not sure how this helps me any better than any of > the other existing testing frameworks do. > > > > http://www.phantomjs.org/ > > This seems to be a headless scriptable WebKit browser. So I could use this > to test my library in the specific version of WebKit this comes with. But > it doesn't sound like it would help me test my library with the various > rendering libraries available in other browsers. I care not only about > WebKit in general, but about the specific versions of WebKit in various > actual versions of Safari and Chrome, the specific versions of Gecko in > various actual versions of Firefox and Camino, and the specific versions of > Presto in various actual versions of Opera. A command-line solution would > be nice too; I know there's a canvas implementation for node (node-canvas) > that I might use for that. But my library will primarily run in the > browser, so I imagine that I'll want to be able to run my test page > directly in various browsers. > > > > The rendering script found in the wiki is pretty cool, but I don't know > if it works with canvas or not: > > http://code.google.com/p/phantomjs/wiki/QuickStart > > It says it does work with canvas: > > http://code.google.com/p/phantomjs/wiki/QuickStart#Canvas > > But that feature seems designed to let you render an entire web page into > an image file. I don't care about that; if anything, I would only want to > render a canvas into an image file, and that's a capability that browsers > already contain (via the toDataURL() method). Ideally I don't want to have > to create an image file from the browser output at all; instead, I would > load the reference image into a browser canvas, use my library to draw to a > second canvas, then compare both canvases. > > > -- > 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 nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
