
| Key: |
SRC-340
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
DK
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Windows XP, IE 6, https Homepage, SES Proxy
|
|
|
The IEHTA has problems with reverse Proxies. Selenium and therefore the browser seem to loose the session they got from the SES reverse proxy.
The error messages of the IEHTA are different and depend on the commands used in the testscript.
The HTA Browser always fails when a clickAndWait command in the testscript is used:
- sometimes the new page is loaded, but the selenium server still waits for the page to load.
- sometimes the element for the clickAndWait command could not be found. But the following page is loading...strange behavior.
- or the testscript terminates because selenium encountered an "access denied" error.
The same homepage can be fully tested with the chrome browser. It seems that the proxy settings of the IEHTA are wrong. The browser must connect our homepage via a proxy. If the browser tries a direct connection or a connection via Selenium the test fails already at the first open command.
Maybe all mistakes have to do with a session that is granted by the reverse proxy, but ignored by selenium.
|
|
Description
|
The IEHTA has problems with reverse Proxies. Selenium and therefore the browser seem to loose the session they got from the SES reverse proxy.
The error messages of the IEHTA are different and depend on the commands used in the testscript.
The HTA Browser always fails when a clickAndWait command in the testscript is used:
- sometimes the new page is loaded, but the selenium server still waits for the page to load.
- sometimes the element for the clickAndWait command could not be found. But the following page is loading...strange behavior.
- or the testscript terminates because selenium encountered an "access denied" error.
The same homepage can be fully tested with the chrome browser. It seems that the proxy settings of the IEHTA are wrong. The browser must connect our homepage via a proxy. If the browser tries a direct connection or a connection via Selenium the test fails already at the first open command.
Maybe all mistakes have to do with a session that is granted by the reverse proxy, but ignored by selenium. |
Show » |
|