Re-enable TestProxies tests
See original GitHub issueWhat is the expected behavior?
Related to Qiskit/qiskit-ibm-provider#304
Currently, test.ibmq.test_proxies.TestProxies
tests are skipped using @skipIf
decorator
@skipIf(sys.version_info >= (3, 7), 'pproxy version not supported in 3.7')
The tests can be re-enabled if we update pproxy
package from version 1.2.2
to 2.1.8
in requirements-dev.txt
file.
Then, test.ibmq.test_proxies.TestProxies
can be run under >= 3.7
python versions.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to Test Proxies: 4 Proven Methods - Proxyway
How to use the proxy checker: Go to the proxy checker's page, enter a list of proxies, and press Submit. After the tests...
Read more >How to Test Proxies: Proven Methods to Check Their Work
To ensure the proxy's quality and reliability, you can use tools like an IP checker to see their geolocation and anonymity.
Read more >How To Test Proxies - Proxyrack
This proxy tester allows you to run configuration transactions once or repeatedly depending on the number of times you set.
Read more >Setting up a Test Agent to act as proxy in tests
To set up and use a Test Agent as a proxy, follow these steps: Allow Internet access for one of the interfaces on...
Read more >What Are Proxy Test Takers (And How to Stop Them) — Caveon
Proxy test taking is when an examinee cheats by having someone more knowledgeable take the exam for them. Proxy test takers can be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, using pip conditionals was the exploration I hinted at by the “play a bit with pip and make it install versions intelligently” !
We are already checking for python version in the test itself and it would be pretty isolated, so there is no worry adding the additional checking and fine-tuning of that parameter - as a matter of fact, some tweaking of the
skipping
will also be needed to account for invalid combinations of python version + pproxy version (mostly for keeping the test suite runnable even under unusual circumstances).There is another solution I thought of @diego-plan9
How does this look to you?
UPD: The only complication with this approach is that
pproxy==1.2.2
uses-i
flag for passing an address, andpproxy==2.1.8
uses-l
flag 😞That would require some checking of python version at runtime: