-
Notifications
You must be signed in to change notification settings - Fork 3
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
Test client #27
Comments
What would this accomplish? |
It would not require to launch a server, so I guess it's faster? And there would be no need to specify a base URL or port in the client. |
Unless I'm mistaken, the test client would have to be specific to each type of framework, yes? |
What kind of difficulties are there with websocket that would be solved with a test client? |
I think so, yes.
Currently, for instance using an |
You mean Starlette's...? |
Yes, sorry. |
My point is that I don't want to shoulder the additional burden of maintaining several test clients if the benefits are only marginal. |
That's perfectly understandable, thanks for the feedback. |
It seems that a real server is used for testing. I was wondering if there could be a test client, similar to what Starlette has, and for instance a
TestFastAPIComponent
that would not start a server?The text was updated successfully, but these errors were encountered: