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.

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

Debug current unit test file #1368

Closed
Djabx opened this issue Apr 11, 2018 · 4 comments
Closed

Debug current unit test file #1368

Djabx opened this issue Apr 11, 2018 · 4 comments
Labels
area-testing feature-request Request for new features or functionality

Comments

@Djabx
Copy link

Djabx commented Apr 11, 2018

Environment data

  • VS Code version: 1.22.1
  • Extension version (available under the Extensions sidebar): 2018.3.1
  • OS and version: Linux Ubuntu 17.10
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.3
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv
  • Relevant/affected Python packages and their versions: XXX

Actual behavior

We can:

  • run current unit test file
  • run all unit test
  • Debug all unit test

Expected behavior

We should be able to:

  • Debug current unit test file

Steps to reproduce:

NA

Logs

NA

@brettcannon brettcannon added feature-request Request for new features or functionality area-testing needs decision labels Apr 11, 2018
@brettcannon
Copy link
Member

Do you mind me asking why you want to debug a specific file versus a single method?

@Djabx
Copy link
Author

Djabx commented Apr 11, 2018

Good question.

Today i had to write a file were some resource (something like a db connection) were not allocated for every tests, but for the entire file (=test suite?).

Every tests alone worked great, but all together some went to error because of the resource that wasn't very well "clean-up" between every tests.

So being able to debug the unit test would have been really helpful (instead of trying to guess why).

Note: but I agree with you, it's the first time I would have needed that.

@brettcannon
Copy link
Member

@Djabx thanks for the info!

@brettcannon
Copy link
Member

We're closing this for now since we have no current plans to do this, but I added it to our overall meta issue tracking testing enhancement ideas so we won't lose track of it when we revisit the topic.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants