-
Notifications
You must be signed in to change notification settings - Fork 20
Docs for running tests #6
Comments
Thanks for pointing that out. As far as I am aware, the tox setup is in an intermittent state. I've started setting it up but never finished. I should either finish that or remove it complete. What I usually do to run the tests and what I am running on Travis is:
This will run all tests except the integration ones that require an account with Amazon. I've added it to issue #7 to write some documentation on that as well. |
Great, I ran that and it appears that all the tests pass. :-) How can I run the integration tests that require an account with Amazon (which I have)?
|
Great 😄 It's always good when tests pass. To run the integration tests you have to run py.test enabling the integration marker:
For it to work you've got set the
Currently the integration tests aren't running on Travis so there might be issues with it because running tests against the MWS API fully automated is tricky because of some of there constraints when creating products. Let me know how it goes and if you have any issues. |
Not so lucky with the integration tests:
|
I've now added a section to the |
I got the latest code, and tried running the integration tests again. I'm getting a lot of errors that look like this:
and
Any ideas why this might be happening? |
That means the integration tests are hitting the MWS API too frequently. The problem here is that getting updates for feed submissions requires polling the API. I've put wait times in several places in the tests to avoid that but it seems that I might have missed some. Is the throttling happening for all tests? Or just some? Can you give more details on where the |
Want me to send you the entire log from running the tests? |
Sure, there's no such thing as too much information, right 😉 |
ok, here they are:
|
I've just checked the throttling limit for |
I changed the INTEGRATION_WAIT_TIME to 60 and re-ran the tests. I'm not getting the request is throttled errors anymore, but still getting failures:
|
This should be fixed in 7d30220, can you give it another go and let me know if it works for you now as well. |
What is the best way to run the tests? I noticed that tox was in the requirements_dev.txt file and there is a pytest.ini file, so I ran this:
Does this mean that all the tests passed? (sorry, I haven't used tox before)
The text was updated successfully, but these errors were encountered: