-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running test against other endpoint? #22
Comments
Hey,
git clone git://github.com/askedrelic/libgreader.git
You need to setup your username/password in the test file, along with changing the ClientAuth to be your new Auth class. You can run the tests in that file, just by calling the file with python. "python test_special_auth.py" will run just the tests in the file. |
Thanks @askedrelic this is exactly what we needed. The gist you sent though has an error which I'm unable to understand: $ python test_special_auth.py
Traceback (most recent call last):
File "test_special_auth.py", line 14, in <module>
echo_feed = [x for x in reader.feeds if "Echo" in x.title][0]
IndexError: list index out of range Any idea what's going on? [it fails for both google reader and our own] Well,n that's just because the feed was not subscribed and hence could not be extracted from the list. |
I'm unable to run the test suite (probably due to my low python knowledge :p):
|
Also, FYI, our Google Reader Compatible API is running at http://readerapi.superfeedr.com/ We'd love to hear your thoughts. |
The
|
Signed up and got things working! Checkout my branch feature/superfeedauth I created a SuperAuthMethod and a seperate test_superfeed.py. Fill in your username and password at the top of the file and then python run it. The user-info stuff works, but I'm category/feed stuff fails due to some |
We (@superfeedr) are trying to produce a compatible Google Reader API, so that it's easy for anyone to change their endpoint and still get their libraries to work.
To achieve that I wanted to know what needed to be changed to run the test suite against our endpoint.
Thanks!
The text was updated successfully, but these errors were encountered: