How to debug pyramid test cases in pycharm 3 - pyramid

I am evaluating Pycharm 3 for pyramid development. My question is how can I debug / set breakpoint pyramid test cases in pycharm 3.
To run test cases, I give following command
python setup.py test -q
I configure this in pycharm, to run test cases from pycharm. But If I set debug pointer / breakpoint, control wont stop. It run test cases without stopping any breakpoint.
Thanks
Aniruddha

See PyCharm documentation on Breakpoints and Debugging.

Related

Is there a way to get printouts from an pyqt5 application built with fbs for Windows without being a debug build?

Use case: Would like to add CLI functionality to a application built with fbs.
When building for Ubuntu it prints out everything when I run this application from the command line, which is what I want. Building with the same settings but for Windows instead I'm not getting any printouts when I try to run this from Powershell or Command Prompt. On Windows the application also seems to be put into the background making it less obvious when it is finished. When application hits an unhandled exception it does not print the error into the command line but into its own window.
Is there a setting you can use to allow printouts for Windows? I know you have a debug build setting which does this but releasing a release as a debug build does not seem right.
cmd /c <name-of-app>.exe This resolves the issue not knowing when the application is done, it does not print out any messages however. It also prints out any unhandled exceptions into its own window.

Can I configure default verbosity in pycharm setting? If so where can I setup that?

Now I'm using terminals to achieve specific verbosity for Pytest framework as below,
I'm looking for default options/settings in pycharm to set my verbosity level as "2" instead of feeding in terminals every time.
Specifications are:
Python 38
Pycharm 2020.3
Pytest 6.2.2
If you've got pytest set up as your default test framework you can modify the test configuration.
When running your test, click on that wrench icon, on the left. It says Modify Run Configuration.
Then, in the context window go to Additional Arguments and type your pytest args. For example:
Finally, when you run the tests, you should see something along the way of:
Launching pytest with arguments -v --tb=long

Unable to run Python files in terminal of VSC

i have installed VSC and set up the necessary dependencies for python.
Using a simple hello world example, i can run the file using run and debug option.
I can also run it by manually typing python hello.py in the terminal.
However, when i use the run button (top right hand corner), i get an error.
Can i check how to solve this?
Thank you.

Is there any way to add arguments to a command in the Nuclide debugger in atom?

I've been trying to get the Nuclide debugger set up in atom. I've installed the atom-ide-ui and atom-ide-debugger-node packages, and can see and open the Nuclide debugger. However, I want to run yarn test_shared as my command, but the debugger only seems to allow a one word command like node or yarn, without any arguments.
Running this would work, but won't actually run my test suite:
This is the command I want to run, but when I launch the debugger it throws this error: Failed to start debugger process: Attribute 'runtimeExecutable' does not exist ('{path}').
Has anyone else found a way to set this up?

eclipse c++ debugging google test with spaces in test name on Linux

I am trying to debug a google test using eclipse (helios) on Linux, when i run a test (without debugging) using --gtest_filter option (example --gtest_filter=Something*) it runs normally.
when i am trying to run the debugger it pop up this error message:
without specifiying arguments the debugger works normally, what could be the problem?
problem Solved.
Solution:
use:
--gtest_filter='Something*' instead of "Something*"
in my case the reason was because of the way eclipse pass arguments to gdb, so the command that will run is:
gdb ./program_name --gtest_filter=Something*
so the * bothers the gdb (maybe think it is paramater for gdb command).

Resources