Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should be interactive #19

Open
turicas opened this issue Sep 17, 2015 · 0 comments
Open

Should be interactive #19

turicas opened this issue Sep 17, 2015 · 0 comments

Comments

@turicas
Copy link

turicas commented Sep 17, 2015

Hello, @brunobord, thanks for your project! :D

A suggestion: instead of waiting for the process to finish execution (using output.communicate()) it would be nice if tdaemon can actually link its stdin/stdout with test runner's stdin/stdout so I can read the output as the test runner outputs it. Another advantage is that I can interact with the test runner (useful when using ipdb to debug).

I'll implement it and create a PR.
turicas added a commit to turicas/tdaemon that referenced this issue Sep 17, 2015
@turicas
Implement interactive call. Fix brunobord#19
57d92c0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@turicas