Cross Browser Testing. Pick a browser, Pick an OS, Test website
11–20 of 48 posts
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#12Earlier quoted context omitted.
I had the same problem. But then I figured out.. you need to enable Java. I get a lot of runtime errors in IE though. Worked great in FF.
Java! Interesting. I did not use that since the 90s. Ok, I enabled Java and reloaded. Then I got "download missing plugins" in that formerly empty space. I clicked on it and then got a window saying "The following plugins are available: Java Runtime Environment". In the meantime, in the background, the page got dark and displayed something about the fact that my session timed out. Anyway, I clicked "next" to continue…
I guess just try again and click through any warnings from FF. If Java works for you on other sites, it should probably work here.
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#13Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#14We really think with ajax this is the only way to do cross browser compatibility. Our site can do screenshots too but you have all the control.
Thanks for checking it out. We will take any feedback good or bad!
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#15I haven't used virtualization on Windows or Linux much, how are those at testing other platforms? All the major browsers already run on Windows, but I've been bitten by differences in Firefox between Windows and OSX before (line heights were off), so multi-OS testing is still important.
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#16Earlier quoted context omitted.
I had the same problem. But then I figured out.. you need to enable Java. I get a lot of runtime errors in IE though. Worked great in FF.
Java! Interesting. I did not use that since the 90s. Ok, I enabled Java and reloaded. Then I got "download missing plugins" in that formerly empty space. I clicked on it and then got a window saying "The following plugins are available: Java Runtime Environment". In the meantime, in the background, the page got dark and displayed something about the fact that my session timed out. Anyway, I clicked "next" to continue…
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#17If I could post a URL I want to test in a form, and be able to select select what browsers I want to test that URL in. And, then, have a script run that would open that URL in each of the web browsers I want to test it in.
That would make a web designer's life much, much easier.
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#18You know what would really make this a killer app? If I could post a URL I want to test in a form, and be able to select select what browsers I want to test that URL in. And, then, have a script run that would open that URL in each of the web browsers I want to test it in. That would make a web designer's life much, much easier.
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#19You know what would really make this a killer app? If I could post a URL I want to test in a form, and be able to select select what browsers I want to test that URL in. And, then, have a script run that would open that URL in each of the web browsers I want to test it in. That would make a web designer's life much, much easier.
I think browsershots.org does that
Put an API on that too so you could integrate it with a testing framework or desktop component (AIR?) without going to the site, and charge incrementally like Amazon does with AWS...
Even with VMWare, I could see myself paying for that.
Re: Cross Browser Testing. Pick a browser, Pick an OS, Test website
#20Great idea. I've been using browsershots.org, which while cheaper only provides static images of pages. Sandboxing the entire machine is a clear improvement. A logical next step is automated testing to take advantage of these system configurations, something like Selenium.
Man, 30 minutes for my screenshots and one of them was completely blank (and it's not locally, so something was with the shot).
How slow would development be if you had to do that!