Hi Nikolas,
Thanks for your suggestion, unfortunately, I don't see how it helps in
my case.
What I'm after is some kind of integration test: when I try to load a
page form the relying instance, verify that it gets redirected to the
provider, and then it gets redirected back with the correct callback
parameters. In both cases I need to actually hit the respective server
running a Django app, since it involves side effects (and side
conditions), such as whether the user is logged in on the provider,
and some in-database state changes to verify that the callback was
valid.
I don't see how mocking a HTTP response would help me with this, but,
of course, I may be missing something here.
Cheers,
Michal
Sorry, I just misunderstood the question. I was thinking of unit tests, in which you'd want to remove as many external components as possible.
-- You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ad81c184-e315-4ada-92f0-23cf7cf86259%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment