|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
Server
|
| Affects Version/s: |
1.0 beta 1
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Especially interesting for O.S. browsers (like IE or Safari) that do not offer per instance proxy settings
|
|
|
For launching in parallel multiple browsers relying on shared system proxy settings (mostly IE and Safari) you want to avoid contention between the different Selenese sessions on setting and restoring these settings. An independendant launcher or monitor could be in charge of setting an restoring the proxy, while all new browser sessions would assume that the proxy is properly set.
This is very similar to what can be achieve with the '*custom' browser, but provide a nicer instrumentation hook and let the user express its actual needs (*safari / *iexplore)
This functionality is critical in providing convenient grid facilities for IE and Safari.
|
|
Description
|
For launching in parallel multiple browsers relying on shared system proxy settings (mostly IE and Safari) you want to avoid contention between the different Selenese sessions on setting and restoring these settings. An independendant launcher or monitor could be in charge of setting an restoring the proxy, while all new browser sessions would assume that the proxy is properly set.
This is very similar to what can be achieve with the '*custom' browser, but provide a nicer instrumentation hook and let the user express its actual needs (*safari / *iexplore)
This functionality is critical in providing convenient grid facilities for IE and Safari. |
Show » |
| There are no comments yet on this issue.
|
|
New Feature
Open
Major
For Distributed Testing (Selenium Grid) the RC should offer a mode where system proxies are not set