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
Utility for providing a sequence of requests/responses to StubTreq #106
Commits on Jul 13, 2015
-
Revert "Remove some code, to make it easier to review. This commit ca…
…n be reverted in a future PR to add this functionality back in." This reverts commit 75b49b1.
Commits on Jul 14, 2015
Commits on Jul 15, 2015
Commits on Jul 17, 2015
-
Ok, omitting interfaces.py from the coverage report doesn't help with…
… codecov, so add it to coverage run too.
-
Revert "Ok, omitting interfaces.py from the coverage report doesn't h…
…elp with codecov, so add it to coverage run too." This reverts commit 3bd122c.
-
Add a consumed() function to sequence, so we can test if the sequence…
… has been consumed.
Commits on Jul 22, 2015
-
Add a consumed context manager, like @radix's awesome consume context…
… manager from effect.testing.SequenceDispatcher
-
-
Commits on Aug 3, 2015
-
Remove our custom ANY, and just have the sequence stubber check for e…
…quivalence. Also add a dodocstring explaining method normalization, url normalization, and headers comparisons.
-
Rename StringSequenceStubs to RequestSequence and change get_response…
…_for to __call__ - thanks @radix
-
Remove RequestSequence's dependency on unit test TestCases, and just …
…have it take failure reporters for now.