AxoCover Run Test Keyboard Shortcut - unit-testing

I'm wondering if there is a keyboard shortcut to run tests with AxoCover from code, like Visual Studio's Ctrl+R+T.

Related

Why does a program that is getting debugged in Visual Studio take focus and not allow me to alt-tab back to VS?

I am trying to debug an application and look at the code while a test runs, but while that test is running the focus is forced on only the application. I can't alt-tab from it back to Visual Studio, because it forces back the focus. How can I look at the code and allow a test to run without it taking focus? This is in C++ and this is not an instance where a breakpoint is being hit

How to put out a Dos screen once you build in Visual studio?

I'm pretty new to programming and I have built my program a few times. However I can't figure out how to make a Command Window or DOS window show up, even after the build has finished in Visual Studio on Windows.
Suppose you have built your program as a 'Console app' or 'Command-Line app' in Visual Studio. These were choices you made when you first set up your project. Then, running your program from Visual Studio will cause a Command Window (DOS like) to display, and your program will start within this window.
The 'Debug' menu item has 'Start Debugging' and 'Start Without Debugging' - either choice will run your program.
Depending on your version of Visual Studio or your configuration options, Visual Studio may close the console window as soon as the program completes. This is not the default behavior on recent Visual Studio options, but you may miss the Console Window popping up and going away if it is happening to you. Likewise, it may be hidden if the Console Window is not displayed as the top-most Window.

Keyboard shortcut for debugging the LAST test run in Visual Studio IDE (2013)

I know there are several VS keyboard shortcuts for running unit tests, but the one I really can't find and would like is to be able to run the last executed test in debug mode.
Ctrl+R, L will repeat the last run, but not in debug mode.
If you are debugging a test, and it changes context to the code you are actually running, and then you stop the test, is there a way to start that test in debug mode again using just the keyboard?
I wanted the same thing.
Based on the technique found in the following post
Visual Studio 2012 debug tests keyboard shortcut
I searched for TestExplorer.DebugSelectedTests and assigned a shortcut key to it.
At least in VS2015 (and hopefully in VS 2013) even while debugging changes context to the code you are actually running. The test remains selected in the test explorer window. So, you can run your shortcut key combo and the test will debug again.
Hope this solves the problem for you too.
I know this question was for Visual Studio 2013, but got google go me here.
In Visual Studio 2019 is a shortcut for that Ctrl+R,D:
If you are using ReSharper, you can use Ctrl+U, D to rerun a test in Debug mode.
https://www.jetbrains.com/resharper/features/unit_testing.html

A step-by-step debugger in C++ win32 projects in visual studio

When I would work on C++ Win32 console applications I would use of F11 for step into and F10 for step over in debugger (DEBUG tab of visual studio, say 2012). But now there function keys don't work as they should in C++ win32 projects. Is there any else method for following code lines in practice in win32 projects like the work that F10 and F11 would do in win32 console applications?
There are buttons for such kind of things in th IDE and it seems really strange that the function keys should not work any longer....
You could also check the settings in Tools -> Options -> Environment -> Keyboard.

GoogleTest: How to set a breakpoint?

I'm using Visual Studio 2010 C++ with Google test. I have a post-build event on my test project to run the test project. This works and the google test test results are displayed in the visual studio output window. However, now I'd like to set a debug breakpoint to step through a test. When I set a break point in either my test code or in the code it calls nothing happens.
How can I set a breakpoint with google test? Or probably more accurately, how can I get it to trigger the debugger?
I guess you have a separate project that builds the test. You should just run it under the debugger.