How to handle browser options for regression testing
For just about any Browser the number of permutations for different settings (security , plugins , privacy, ect.) are overwhelming. How do you handle this in regression. It's just not feasible to cover any significant portion of different settings. Is it acceptable to just test with defaults ?
Re: How to handle browser options for regression testing
It depends on the site that you are testing. You could use a risk-based approach to decide which options to test. I would imagine that most of your testing would be done with the defaults although it would be wise to do some with a non-default setup too. Make sure that your test plan states assumptions about what settings will be in place for testing before it is signed off so people get the chance to comment.