Skip to content
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

Use django-webtest instead of the built in client #5

Open
thedrow opened this issue Dec 2, 2013 · 3 comments
Open

Use django-webtest instead of the built in client #5

thedrow opened this issue Dec 2, 2013 · 3 comments

Comments

@thedrow
Copy link

thedrow commented Dec 2, 2013

The build in client is not suitable for smoke testing.

https://github.com/kmike/django-webtest

@thedrow
Copy link
Author

thedrow commented Dec 2, 2013

Actually I'm not sure about it. Django now uses WSGI when you use the LiveServerTestCase.
Maybe you can still borrow some ideas like form smoke testing.

@mattrobenolt
Copy link
Owner

What's wrong with the built-in client? What features are lacking that you'd want from an external library?

@thedrow
Copy link
Author

thedrow commented Dec 2, 2013

First of all, there's no support for the patch HTTP method. DRF's APIClient might be enough for me at the moment.
I can think of other usecases but not right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants