-
Notifications
You must be signed in to change notification settings - Fork 259
Multi-Browser Support #39
Comments
Hey, your right(ish). I don't personally see PhantomCSS as x-browser testing tool, products like BrowserStack do a pretty good job of that. That said, PhantomCSS is just a module/extension of CasperJS. CasperJS is working on support for Gecko and Trident so potentially, hopefully, with little if any changes to PhantomCSS visual testing of those browser engines might become possible. https://github.com/n1k0/casperjs/issues/688 / http://triflejs.org / http://slimerjs.org/ I haven't got SlimerJS working yet, I haven't had the time - but it might work now if you want to have a go. |
I was able to run CasperJS + SlimerJS (by just dumping the contents of each in one folder). |
Would it be helpful to remove the dependency on CasperJs and instead go with WebDriverJs? I like the interface CasperJs gives, but Selenium seems to be the dominant player. |
If WebdriverJS support can be added without making the library overly complex then that would be a great step forward. I discovered this https://github.com/webdriverjs/webdrivercss the other day, which I think is a great idea! For me, PhantomCSS is not a x-browser visual testing tool. I don't even use it in end-to-end testing. PhantomCSS (for me, and Huddle) is a unit testing tool for CSS and layout. Primarily I want feedback from these tests to be as fast as possible. A parallelised headless-browser with minimal dependencies will always be faster than Selenium, even Selenium Grid. But that's not to say that x-browser or Selenium integration wouldn't be very cool. |
Has anyone looked into integrating this with a saucelabs like service for cross browser visual testing yet? |
Hate to leave a simple +1 comment, but integrating this with SauceLabs would be awesome. |
Up! Any updates regarding other browsers like Opera, Safari and the evil IE? |
Even though this project is named PhantomCSS, it would be great if you gave the option of testing in different browsers.
Because as we all know, Chrome != Firefox != IE != ...
The text was updated successfully, but these errors were encountered: