Thanks. Weirdly, issue was resolved when I cleared my cache and restarted browser.
On Nov 6, 1:55 am, Tony <[EMAIL PROTECTED]> wrote: > HiMaven, > > This is just a suggestion ... and others might have better ones > When testing a website (usually test env) certificates might expire > and get renewed. > Hence putting the code to click on the continue button on certificate > Window into the testcase is not usually a good idea. > Cause when the certificate is renewed .. your testcode might break or > would have to have a better way to manage the warnings. > > Certificate being always valid is an assumption that we can make .. > since we are not testing this but the functionality of the website. > Certificates in the production env would be different. > > Make the autoit code to run separately(different process) and click on > any certificate windows that popup automatically. > Hence your test code will run when popups exist or dont. > Also when you have valid certificates and run them through a proxy > like fiddler .. you will definitely get the certificate warning > messages. > > Iam not sure on the problem that when you run it manually, you got the > warning and when running it through the script you didnt get it. > Maybe you clicked on some some checkbox to disable the warning. > > - Tony --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
