Vital Kudzelka

Hi @fuhrysteve! This changes looks good for me. But `live_server_subprocess` fixture can be always available (not only when `pytest-service` is exists). It would be great if `live_server_subprocess` fixture can detect...

Use the separate `--start-live-server-subprocess` option to run `live_server` fixture as subprocess is another suggestion. Any thoughts?

> the reason is that `watcher_getter` would fail because it says it can't find a fixture with that name I missed that part, maybe I can find a workaround.

What do you mean? On Mon, 25 Jan 2016 5:38 am tanyewei [email protected] wrote: > how to testing flask-login? > > — > Reply to this email directly or view...

> trouble with cookies because client doesn't have the expected scope What is the _expected scope_? You can always **explicitly** create required scope by passing any headers into the client....

If there's nothing else I'm closing this issue. @tanyewei feel free to reopen it.

@tmehlinger thank you for clarifications. For now request context has been pushed to ensure the `url_for` can be used inside tests without any configuration. The same feature can be achieved...

Hi @hackrole! As mentioned above, the `client` fixture pushes a new request context, so the 1st example doesn’t work because the `current_user` is anonymous. The alternate approach is explicitly pass...

Hi @martinpengellyphillips! Thank you for the report. Sadly I have no possibility to reproduce or test your issue, but looks like it can be easily fixed. Please, test against `54-pickle-error-on-windows`...

I‘m sorry, but I‘m not sure I can be of much help (I don‘t run windows), but if you come up with a solution (or someone else), I‘ll happily review...