Selenium1.0beta for Firefox3 is ready

We have fixed most of blocking bugs on Firefox3. It's time to upgrade our Selenium lab machines to Firefox3.0.5. Mozilla has announced Firefox2.0.0.20 would be the last version and stopped Firefox2 maintenance & supports. The Firefox3 market share is increasing to 17% at the end of 2008.


The interesting new issue on Firefox3 is SSL cert exception page blocking Selenium automation. On Firefox2, we invoke RMD.xpi XPCOM in Selenium to intercept all bad cert exception for our self-signed certificates. However, it doesn't work on Firefox3 now that RMD.xpi's author said it only supported Firefox2. Firefox3 introduced a new SSL certificate exception rule. We must find a new workaround.

Block step:


Try below selenium ssl test case:

 
<tr>
 <td>open</td>
 <td>http://kuix.de/mozilla/certwarndiscussion/proposal20061016/</td>
 <td></td>
</tr>
<tr>
 <td>open</td>
 <td>https://www.cacert.org</td>
 <td></td>
</tr>
<tr>
 <td>open</td>
 <td>https://www.kuix.de</td>
 <td></td>
</tr>
<tr>
 <td>open</td>
 <td>https://mur.at</td>
 <td></td>
</tr>
<tr>
 <td>open</td>
 <td>https://kuix.de:9443</td>
 <td></td>
</tr>
<tr>
 <td>open</td>
 <td>https://www.kuix.de:9443</td>
 <td></td>
</tr>

I plan to create a new project 'Remember Certificate Exception'(RCE) on AMO today. The RCE.xpi's purpose is auto-complete Firefox3 certificate exception override.