4 ms·

There's really no excuse for not testing in all browsers but I can understand the impulse to "get the change out the door" too. For myself I tend to iplement a

by SamAtt 17y ago

There's really no excuse for not testing in all browsers but I can understand the impulse to "get the change out the door" too. For myself I tend to iplement a change in a separate file and leave the old page in place. Then as I test each browser I use the browser ID to redirect people to the changed page as I test their browser. Then when I'm done I replace the old page and remove the redirect. It sounds strange but I've found it's a good way to get changes out as soon as possible while not risking what happen to the author here.

jhancock 17y ago
The excuse for not testing on all browsers is that its incredibly time consuming. It also requires you to be at your main workstation that has all those test VMs.
- thaumaturgy 17y ago
  I will take this opportunity to keep plugging for http://crossbrowsertesting.com/ http://crossbrowsertesting.com/ I'm not affiliated with them in any way, they've just made my one of my jobs much easier for not much money, and they hang out on HN sometimes besides.
  - systemtrigger 17y ago
    Others: Adobe BrowserLab and LitmusApp. BrowserLab is fast and free. LitmusApp is much slower and costs us $49/month but it has some advantages - it has a good series processing UI, it links to w3c html and css validation results, and it doesn't crop the bottom of the page.
  - jhancock 17y ago
    good plug. I'm fairly certain to start using tools like this as managing "test VMs" is a PITA.
  - tonetheman 17y ago
    Not sure if you have tried the new bookmarklet we released, but it changes the way you interact with the service. In two clicks (click on the bookmarklet, click on the browser / platform you want to test in), the page you are currently viewing is launched in the remote configuration and the browser is opened to your current page. It really improves the work flow. You can read more about it at http://crossbrowsertesting.com/blog/new-cool-bookmarklet http://crossbrowsertesting.com/blog/new-cool-bookmarklet. Appreciate the plug! Tony Founder - CrossBrowserTesting.com

by SamAtt 17y ago

jhancock 17y ago

The excuse for not testing on all browsers is that its incredibly time consuming. It also requires you to be at your main workstation that has all those test VMs.

thaumaturgy 17y ago
I will take this opportunity to keep plugging for http://crossbrowsertesting.com/ http://crossbrowsertesting.com/ I'm not affiliated with them in any way, they've just made my one of my jobs much easier for not much money, and they hang out on HN sometimes besides.
- systemtrigger 17y ago
  Others: Adobe BrowserLab and LitmusApp. BrowserLab is fast and free. LitmusApp is much slower and costs us $49/month but it has some advantages - it has a good series processing UI, it links to w3c html and css validation results, and it doesn't crop the bottom of the page.
- jhancock 17y ago
  good plug. I'm fairly certain to start using tools like this as managing "test VMs" is a PITA.
- tonetheman 17y ago
  Not sure if you have tried the new bookmarklet we released, but it changes the way you interact with the service. In two clicks (click on the bookmarklet, click on the browser / platform you want to test in), the page you are currently viewing is launched in the remote configuration and the browser is opened to your current page. It really improves the work flow. You can read more about it at http://crossbrowsertesting.com/blog/new-cool-bookmarklet http://crossbrowsertesting.com/blog/new-cool-bookmarklet. Appreciate the plug! Tony Founder - CrossBrowserTesting.com