If you were talking to someone whose organization is considering CrossBrowserTesting, what would you say?
How would you rate it and why? Any other tips or advice?
Being able to test against our local development machine is key too. We don't pollute our QA server until we're ready for actual QA and we can find out what's going on much quicker than a check-in/deploy/test/redo cycle that would normally be needed if it weren't for the ability to test locally. This works and it works well and is a great addition to our testing toolbox. Overall, the product does what we need and does it well.
Agile Support Test script feature Graphical Test Reports Dashboard Widgets
Go for it!