Matijs van Zuijlen

There are a couple more commits on #505 that I haven't added yet.

Aruba should definitely support this.

I think what happens here is this: * The non-interactive command finishes and sets `@last_command_stopped`. * The interactive command gets started and is told to finish by the fake user,...

I think this issue still exists & I'm going to take a look at it.

I've looked again at the 0.6.2 implementation, and it stops all processes unless it has deliberately stopped a process before. In the case of this scenario, this means it stops...

@mroth I'm afraid you will have to add some step that waits for the interactive command to finish. This would be either `I stop the command started last` or `"I...

Documentation about this should probably be improved, since the interaction between steps is not very clear in this case. A step definition like `I let the command started last finish`...

Yes, I'll do a rebase.

.. maybe even split it up so at least the build runs with the correct ruby versions.

Specs are green :tada:. Now for the features :construction: :construction_worker_man: :construction_worker_woman: :building_construction: