A test automation library based on common other best practice open source libraries. It adds missing functionalities but does not reinvent the wheel. Just glues stuff together nicely and adds some sprinkles.
MIT License
80
stars
11
forks
source link
Add possibility to use credentials on a HTTP proxy #299
We do have the possibility to configure a proxy inside Neodymium. If the proxy is a socks proxy, we can use authentication. For HTTP proxies however this is currently not possible.
Since webpages can use geolocation lookups to provide specific versions of their page, having a secured proxy would be great.
User Story
As a testautomation engineer,
I want to simply configure an authentication for a given HTTP proxy
so that I can access pages, which are accessible from certain geolocations only
Functional Requirements
[ ] Add a way to use a proxy with an authentication via our configuration
[ ] Add neodymium.proxy.userName and neodymium.proxy.password properties to configure this proxy
Documentation Requirements
[ ] Document the new configuration accordingly in our wiki
Test Requirements
[ ] Do a smoke test on an external test suite like the neodymium example with a given proxy
[ ] Add unit tests as far as possible
Additional Information
A possible solution was done for a customer project. Ask @oomelianchuk for details on this.
Quick Description
We do have the possibility to configure a proxy inside Neodymium. If the proxy is a socks proxy, we can use authentication. For HTTP proxies however this is currently not possible. Since webpages can use geolocation lookups to provide specific versions of their page, having a secured proxy would be great.
User Story
As a testautomation engineer, I want to simply configure an authentication for a given HTTP proxy so that I can access pages, which are accessible from certain geolocations only
Functional Requirements
Documentation Requirements
Test Requirements
Additional Information
A possible solution was done for a customer project. Ask @oomelianchuk for details on this.