I just upgraded to Xcode 6.3 and I have lost the unit test status/run indicators that were displayed in the left gutter of the editor. The status/run indicators don't immediately show in the Test Navigator either until after I perform a compile and test (Ctrl-U). After the tests have run the Test Navigator will display the status/run indicators but the status/run indicators in the editor are never displayed.
Has anyone else noticed this? I would really need to get these back. I hope someone knows how to fix this.
Thanks in advance.
Sorry. I thought I'd read through the Apple's latest release notes for Xcode, but I apparently missed this part. Thanks anyway.
Swift tests are not automatically discovered in this release of Xcode.
Test annotations in the source editor sidebar will not appear, and the
test navigator and the table of tests in the Test action of the scheme
sheet will be empty. You can run Swift tests by selecting Product >
Test. Once tests have been run, they appear in the test navigator and
the scheme sheet. The following limitations apply:
Tests discovered through execution in this manner provide limited
interaction in the test navigator. For example, Run buttons do not
appear and clicking on a test in the navigator does not jump to the
source code except in the case of a test error. Run buttons and test
success/fail indicators will not appear in the source editor.
(20373533)
This bug in XCode 6.3 is fixed in XCode 6.3.1.
Gerd
Related
I have a solution with a test project in it, based on nUnit. All of the tests I created show in the test explorer window, I can execute, etc.
I added another unit test project to the solution, created references exactly like the first project, same nUnit version, same Platform target (Any CPU), same code structure, etc., just for a different product. But I added tests (with Test attribute) to that project and they don't show in the Test Explorer.
All of my tests in the original project still show but no tests in my new project show.
How do I get tests from multiple projects to show in the Test Explorer window?
Is the Test Explorer window tied to a specific project?
I spent a day trying to figure this out but once I posted the question, as luck would have it, I figured out the solution. I changed the nUnit version back to 3.7.1.0 and it works - both projects now show tests in the Test Explorer window.
I just installed Visual Studio 2013 Premium and was having a good time playing with it and writing unit tests (using MS unit tests). However, the "Test Lists" window and some other Test related windows suddenly disappeared AND they have disappeared from the menu item
Test->Windows. In fact I remember Test->Windows having 4 items under it and now I only see two: Test Explorer, Code Coverage Results. i stress they WERE present in Visual Studio 2013. Clearly, I hit some key combination that made them disappear or something happened to make them disappear. How do I get Test List back? Please don't see they are under Tests->Windows, because for me, they are not (at least now. they were!)
Anyone else seen this? Any solutions? I tried restarting Visual Studio, rebooting.
Also, previously, under the "Test" menu, there was a Debug->"Test in Context" and a Run->"Test in Context", or something like this. It was very handy. If your cursor was with in some test, you could run just that one. I'm guessing this is related.
For all I know, these features have been "optimized" into the new test-window... a.k.a. they have been removed. Some other unit test related features are also gone (the context menu item for "create unit tests" is gone for example, yet can still be called via the command window)
Personally I think this is Microsoft's way of pushing everybody towards the Team Foundation Server but that's just my two cents.
I just had the same issue. In my case I needed to install the NUnit plugin ("Nunit test adapter"). After restarting the tests came back.
Start Developer Command Prompt:
cd to UnitTest-folder\bin\Debug which contains .dll
enter command: mstest /testcontainer:UnitTestMyTest.dll
(this creates the test-result)
in VS:
menu View / Other Windows / Test Results
manage Test Runs: window Test Runs -> connect to Test Run
browse to test-folder\bin\Debug\TestResults
I'm using Eclipse Kepler CDT with Google Test. Unit testing is working fine, but I can't find a way to get a shortcut to run all unit testing. Everytime I need to run test, I have to click the little arrow near the run button and select the unit test icon.
I can't find c++ unit test in the "Keys" menu (although Run JUnit test is available).
Still you can use Ctrl+F11 to launch the last Run Configuration, so launch once your tests by clicking, and then hit Ctrl+F11.
CTRL+F11 to work the way you want, you must set (from "Windows/Preferences") the
"Run/debug > Launching : Launch Operation" setting to:
Answer in this post.
https://stackoverflow.com/a/1152039
When a test hangs in a loop, the small green progress bar in the test runner does not proceed, but there is no way to stop the test run. Or is there?
VS 2013
Edit: This occured when using the XUnit TestRunner. The Cancel button simply did not show up. After testing various test runners in a new solution, it turned out, that it works with all of them. Finally it also worked with my original solution. So there was some anomaly in the state of my VS environment that caused cancel to disapper.
You can click "Cancel" in Test Explorer:
Show Test Explorer by going to TEST > Windows > Test Explorer.
This is in Visual Studio 2013.
Instructions for other versions of VS can be found here
Sorry for waking up an old thread:)
just wanted to share my solution here, I had the same issue on VS 2015.
There is some text below the search input just where the cancel should appear (take a look at #Codeman print screen), the text is actually some description on how you can setup a build for your tests, the text is several lines and at the end you have "do not show this any more" just press it and then the cancel button appears:)
Very strange bug, sorry I do not have some print screens of this
hope it helps someone
VS2015. If the hanging tests are executables instead of DLLs you need to kill those tests in the task manager. You need to close the Test Explorer Window to prevent automatic running. While the tests are running/hanging you will not be able to compile the according project.
For me the solution was to go to Task Manager, locate chromedriver and end the task.
Visual Studio 2022 Professional version 17.2.3.
I have found the solution to this issue. To stop the run after cancel is pressed, just set the 'Terminate process on cancel' option to True.
As the title says, the coloring is not working. If I to go tools > options and look for 'Coverage Touched' etc in the list of Fonts and Colors, they don't exist there.
If I run the tests with the option to analyse them for coverage, no colors show up in the editor. I have VS 2012 Premium update 3 installed.
I already:
resetted usersettings
ran in safemode (can't run tests then, so useless)
re-installed VS
rebooted everything
A colleague of mine used the exact same installer/image, and it works for him...
Any ideas anyone?
I resetted Userdata (for the 10th time) and I noticed that by default it migrates the settings from 2010 or something. I now unmarked that checkbox, and the problem is now solved.
I'm not 100% sure if the checkbox was the problem, but thats the only difference I can recall.