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

Pycharm support #42

Open
dimberman opened this issue Mar 22, 2022 · 4 comments
Open

Pycharm support #42

dimberman opened this issue Mar 22, 2022 · 4 comments
Labels
external needs fix or support from 3rd party

Comments

@dimberman
Copy link

Hello all!

I'm testing out the library right now and I'm noticing that if I create describe scenarios in pycharm there doesn't seem to be a way to run single test. For normal pytest or unittest tests I can see a play button that allows running just that test
Screen Shot 2022-03-22 at 11 51 18 AM

However when I try to run a pytest-describe scenario it seems I have to run the entire file to get those tests to run
Screen Shot 2022-03-22 at 11 51 26 AM

Is there something I can do to have pycharm recognize this? I didn't see a specific pytest-describe plugin

@miinx
Copy link

miinx commented May 9, 2022

Upvote! 👍

@qutax
Copy link

qutax commented May 23, 2022

It probably needs to be resolved in the IDE.

However, you can run the tests via the IDE without the buttons:
If you click somewhere in the file in the editor window and press the "Run 'Python tests in test…'" shortcut (by default Ctrl + Shift + F10 for Windows and Linux and Control + Shift + R for MacOS) the tests should be executed via the IDE.

@jwsloan
Copy link

jwsloan commented Feb 1, 2023

@dimberman we noticed the same problem. If you still prefix your test names with test_, then PyCharm will pick those up and let you run them individually. They will also still roll up under the describe block in the output. It's the best of both worlds! :)

@Cito
Copy link
Member

Cito commented Apr 9, 2023

I've created a PyCharm issue now asking for support on the end of PyCharm. I don't think it's a big usability issue, but of course would be nice if that would be supported there.

Thanks @qutax and @jwsloan for posting the workarounds.

@Cito Cito added the external needs fix or support from 3rd party label Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external needs fix or support from 3rd party
Projects
None yet
Development

No branches or pull requests

5 participants