Issue when the test asks for prompt

[broxane]

Hi, it's me again, and it is again about a django-related behaviour.

Sometimes, when you stop a test with ctrl+C (or when the test failed to execute, for instance because of a syntax error), the test database could not be exited properly, so the next time a test is run, you have this prompt :

Creating test database for alias 'default'...
Got an error creating the test database: database "test" already exists

Type 'yes' if you would like to try deleting the test database 'test', or 'no' to cancel: 

Mutmut does not like it very much :

• At phase 1 - mutmut wait indefinitely
• At phase 2 - the test is considered as timeout ⏰

[broxane]

Once again, sorry for approximate english

[boxed]

Interesting. I find it a bit weird that you'd end up in that state due to a syntax error in the source code, but let's leave that aside as you already have issues open for that..

I guess we could be gentler when shutting down. Maybe sending a signal to the testing process and waiting for a timeout. The user could kill hard by pressing ctrl+c again. We should make it clear that we are waiting and that you can kill hard with a second ctrl+c.

[broxane]

As I see it, the issue is more about reacting when the test asks for a prompt, rather than exiting gently, especially when it can be due to another suit of tests... Do you see what I mean ?

[boxed]

I think that needs to be fixed too, but if we just handle this you'll still not be able to get this to work.

[bskinn]

@broxane As a shim for this hangup, you may be able to use my stdio_mgr package within your test function/method... it patches out stdin, as well as stdout/stderr. You preload stdin with a response to the prompt, which is supplied when the enclosed code calls input():

from stdio_mgr import stdio_mgr
with stdio_mgr("yes\n") as (in_, out_, err_):
    {code for creating 'test' database, consuming the provided "yes\n"}
    # If you want, you could test for the database-exists prompt with something like:
    assert 'database "test" already exists' in out_.getvalue()

The test should still run fine (without that above assert) even if the 'yes/no' prompt doesn't occur, b/c the pre-loaded "yes\n" would just be discarded.