Thursday, August 13, 2009

os / browser testing

Couple of aspects / challenges to solve
  1. There are tones of possible OS/Browser/plugin configurations. Maintaining each of them can be costly and resource intensive
  2. Supporting closed source stuff like Windows, Apple can be costly just for the price of OS alone
  3. Open Source (Linux) has the challenge of variety -
  4. Blackberry, iPhone OS, Symbian OS - nooo don't open that Pandora Box
  5. How do we make Windows XP multiple concurrent users
  6. How to remotely access the desktop with lowest network bandwidth cost
  7. How to have no/minimal client side setup
  8. How deal with variety in clients (Windows, Mac, Linux, IE, FireFox, Safari....) accessing our solution
  9. How to ensure (and verifiable?!) privacy of customer installation
  10. How to get the first 1-100 customers. The next 10,000 can be easy (as each of them want to do it on their own - wouldn't they)
  11. How to price for casual one time user (read as freelance web site designers)
  12. How to prevent folks using us as launch pad for attacks

What are the comparable technologies out there we can adopt
  1. Virtual machines
  2. VPN
  3. WebEx (any solution from Citrix? I believe yes)
  4. litmusapp.com
  5. cloud computing
  6. http://www.soti.net/
  7. http://browsershots.org/
  8. http://www.browsercam.com/
  9. http://webworkerdaily.com/2008/01/07/is-your-html-good-enough-7-browser-testing-services/
  10. http://tredosoft.com/Multiple_IE
  11. http://www.xenocode.com/browsers/
  12. xWindows - http://www.straightrunning.com/XmingNotes/
  13. http://saucelabs.com/
How about I operate on one os/browser - but the same http response is rendered on different os on multiple screens in front of me...

Blog Archive