-
Notifications
You must be signed in to change notification settings - Fork 110
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
Re-use app in LiveServerTestCase subclass #115
Comments
I can see the usefulness for a feature like that. I would like it to be controlled by a class level flag that defaults to the current behavior to maintain backwards compatibility and give users of the library the option about whether they want this behavior in their TestCase class or not. If you get a PR together, I can take a look at it. |
I now achieved almost what I wanted with an env variabele that let's the developer choose between the LiveCaseServer or the normal flask one, but this makes it more difficult to integrate in the CI, as the server has to be running in background mode (not ideal): This doesn't use the LiveTestCase server but relies on the user starting it's own:
|
First of all: thanks for this excellent testing project :)
I subclassed LiveServerTestCase to do some acceptance testing, and run it in a py.test env. In our case the startup of the app is rather expensive as it needs to connect to a SOAP server with a big wsdl, startup time around 5-6 seconds. Is there a way to reuse the already running app for test in the same TestCase class? Now the app is teared down and (re)started after each test.
The text was updated successfully, but these errors were encountered: