The only step necessary to automate accepting a certificate when running a test in Internet Explorer is to accept it once, permanently. This must be done manually. After this, Squish will tell Internet Explorer to use the accepted certificate on each test run, and no further manual intervention is required.

To accept a certificate in Firefox, you must add some code to your script that will automate the browser dialogs for accepting the certificate. In addition it is necessary to work around an issue in Firefox would make the test case hang. To do this, first a temporary site must be loaded, and then the real site can be loaded.

Here is an example that shows how to automate connecting to an HTTPS site and accepting the certificate.

# Workaround: Load a temporary page first
loadUrl("http://www.froglogic.com")
# Now load the real page
loadUrl("https://the.real.site.you.want.to.load")
if Browser.type() == Browser.Firefox:
    # Accept the certificate
    waitFor("isBrowserDialogOpen()")
    nativeType("<Return>")
    snooze(1)
    # Accept the second certificate dialog
    nativeType("<Left>")
    nativeType("<Return>")
    waitFor("!isBrowserDialogOpen()")
    rehook()

// Workaround: Load a temporary page first
loadUrl("http://www.froglogic.com");
// Now load the real page
loadUrl("https://the.real.site.you.want.to.load");
if (Browser.type() == Browser.Firefox) {
    // Accept the certificate
    waitFor("isBrowserDialogOpen()");
    nativeType("<Return>");
    snooze(1);
    // Accept the second certificate dialog
    nativeType("<Left>");
    nativeType("<Return>");
    waitFor("!isBrowserDialogOpen()");
    rehook();
}

# Workaround: Load a temporary page first
loadUrl("http://www.froglogic.com");
# Now load the real page
loadUrl("https://the.real.site.you.want.to.load");
if (Browser.type() == Browser.Firefox) {
    # Accept the certificate
    waitFor("isBrowserDialogOpen()");
    nativeType("<Return>");
    snooze(1);
    # Accept the second certificate dialog
    nativeType("<Left>");
    nativeType("<Return>");
    waitFor("!isBrowserDialogOpen()");
    rehook();
}

# Workaround: Load a temporary page first
loadUrl "http://www.froglogic.com"
# Now load the real page
loadUrl "https://the.real.site.you.want.to.load"
if {[[invoke Browser type] == Browser.Firefox]} {
    # Accept the certificate
    waitFor "[isBrowserDialogOpen]"
    invoke nativeType "<Return>"
    snooze 1
    # Accept the second certificate dialog
    invoke nativeType "<Left>"
    invoke nativeType "<Return>"
    waitFor "![isBrowserDialogOpen]"
    rehook
}

Loading the temporary page is just an unfortunate—but hardly noticable—necessity. Once the page has loaded, Firefox uses two dialogs to complete the acceptance of a certificate, so we must interact with both of them to complete the acceptance. We use the nativeType function to simulate the keyboard interaction, where normally we'd use the type function. Also, after interacting with the dialogs we must call the rehook function to make Squish do some reloading and reinitialization to account for the fact that the certificate has now been accepted and that as a result, the web page is in a different state.

The only step necessary to automate accepting a certificate when running a test in Safari is to accept it once, permanently. This must be done manually: First, open the page with the certificate in Safari, then choose to view the details of the certificate in the sheet that pops up, then check the checkbox that tells Safari to always trust the certificate on reconnects. After this, Squish will tell Safari to use the accepted certificate on each test run, and no further manual intervention is required.