It seems to be that one of the biggest pains of being a web developer is having to support legacy browsers. There's no denying that when you approach a high volume of customers, the marginal gains of a 1-3% increase in userbase can have a worthwhile effect in revenue.
Also, with a lot of corporations requiring their employees to use IE8, they can represent an integral market if your software's goal is to aide people at work.
My question is how do you reduce the pain and time it takes to test your app / website / service over many different browsers and operating systems?
Do you contract it out? Do it in house? Rely on previous experience and have a list of what not to do's for certain browsers?
It seems to be that one of the biggest pains of being a web developer is having to support legacy browsers. There's no denying that when you approach a high volume of customers, the marginal gains of a 1-3% increase in userbase can have a worthwhile effect in revenue.
Also, with a lot of corporations requiring their employees to use IE8, they can represent an integral market if your software's goal is to aide people at work.
My question is how do you reduce the pain and time it takes to test your app / website / service over many different browsers and operating systems?
Do you contract it out? Do it in house? Rely on previous experience and have a list of what not to do's for certain browsers?
Peace,
ABNWZ