inetcpl.cpl not clearing SSL cache when tests are run from ALM

[msacks]

I have a set of test scripts that use different certificates. Each script begins by opening IE and then calling a function to run inetcpl.cpl to clear the SSL cache. That way I can run Script1 with Cert1, Script2 with Cert2, etc. in the same ALM test set. The script ends with the browser closing, so the next script runs from scratch.

However, a recent change to Windows 7 has made this solution not work. Now the SSL cache is only cleared once all IE sessions are closed, not just the one running the test. This means that the script calling Cert2 will fail because Cert1 is still in operation. Of course, in order to run the enter test set, ALM has to be open in a browser that does not close between tests.

Is there any way to clear the SSL cache in the browser running the test without closing the browser that is running ALM?

[supputuri]

I have a set of test scripts that use different certificates. Each script begins by opening IE and then calling a function to run inetcpl.cpl to clear the SSL cache. That way I can run Script1 with Cert1, Script2 with Cert2, etc. in the same ALM test set. The script ends with the browser closing, so the next script runs from scratch.

However, a recent change to Windows 7 has made this solution not work. Now the SSL cache is only cleared once all IE sessions are closed, not just the one running the test. This means that the script calling Cert2 will fail because Cert1 is still in operation. Of course, in order to run the enter test set, ALM has to be open in a browser that does not close between tests.

Is there any way to clear the SSL cache in the browser running the test without closing the browser that is running ALM?

Quick thing that you can try is, install Fire IE from the below link and open the ALM in Firefox. Then run your test as usual.

Fire IE (IE in Firefox)

Let us know if this helps.

[msacks]

I tried this but have not been able to get Fire IE to work. However, I have another workaround, which is to run ALM from one machine and have it run the tests remotely on another.

Thanks for the suggestion, though. I may keep playing with it.