The easiest way to do it is to enable straight http:// in your dev
environment, test everything automated, then turn on https:// and do
enough manual testing to build confidence that your software works
identically under both environments. The biggest problem we've had is
that our export to word (.rtf) seems to cut out the images in https://
but work just fine under http. Otherwise, it's pretty much the same.
You can also configure sellenium to use the cybervillans certificate
(
http://selenium-rc.openqa.org/tutorial.html#https ) - but that's
basically telling it to bypass the very secrutiy functionality you are
trying to test! So be sure you do manual testing before you release it
to the world!
Hey, anybody planning on GTAC 2008? It's in Seattle. We should
invite Jon Bach. (This guys -
http://video.google.com/videoplay?docid=7894844001159492923&q=jon+bach+tech+talk&ei=RBAXSMPtM4rQ4gL1mNHkBg&hl=en
)
Regards,
--heusser
Check out my blog "matt heusser solves all your problems with software
testing"
xndev.blogspot.com
(Ok, maybe not. Check it out anyway ...)