After updating to latest Android Studio version (3.6.1), JUnit logs changed a bit.
One of the things I recently noticed is that every new Test the log is adding a couple of new empty lines to the test log.
This becomes increasingly bad in our project that has thousands of tests, as it becomes difficult to see if any UT sent a crash log but assertion resulted ok.
Any known way to deactivate this behavior?
Added lines:
Reduced lines:
NVM it is fixed in the newest Android Studio 4.0
Related
I have an issue very similar to this one.
Debugging any test in Resharper returns "Inconclusive: test not run". This occurs for every test, every solution, every project at my machine. Reinstalling VS2019 and Resharper didn't help. Running tests works fine.
I've debugged test using devenv.exe /ReSharper.LogFile C:\temp\resharper.log /ReSharper.LogLevel Verbose command and the result is this (a fragment of ~6900 lines file).
The first error says: “Method 'StartSessionAsync' in type 'ReSharperAwareWrapper' from assembly 'JetBrains.ReSharper.UnitTesting.MSTest.Provider, Version=777.0.0.0, Culture=neutral, PublicKeyToken=1010a0d8d6380325' does not have an implementation.”
I tried all the popular answers in the post I've linked and nothing seems to help.
Code is .NET Core 3.1 based C# solution.
Resharper: 2020.1.4 | Visual Studio: 16.7.0
I've solved an issue by installing 2020 EAP version of resharper (2020.2 EAP). Seems like it's a bug in 2020.1.4 version.
I started to have exactly the same issue after i updated VS to 16.7. Funny thing is that it broke unit test debugging in Rider as well.
Microsoft has pushed new Microsoft.NET.Test.Sdk package, but looks like it does not help. As a workaround, you can launch test from VS Unit Test window, instead of Resharper's one.
For me it was because the test was unchecked at build time. So I had to checked the Unit Test projects in
Build -> Configuration Manager . check column build.
As #Peace says, you can update ReSharper, but if that does not help you can:
Reboot
Update Visual Studio: Help > Check for Updates
In addition to the answer given by #Mihails Popovs. Possible cause is that you do not have referenced the Microsoft.NET.Test.Sdk.
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 am trying to install NCover in an existing C# .NET project for work. Unfortunately, after I download NCover and installed the Visual Studio extension, it wasn't finding any of the unit tests. The answers I've seen/heard seem to be in the vain of 'It wasn't working...time passed...it started working.'
I can run the tests with Visual Studio's Test Explorer, but I need to get NCover installed to see the code coverage. I had NCover installed previously, and other people on my team are getting it to work within the same project.
I am using Visual Studio 2013 with the newest version of NCover Desktop (v 5.1).
I am getting two errors in the console log.
The first switches between saying:
Agent Error (v4x64): An error occurred while loading assembly
and
Agent Error (v4x64): There was a problem loading test assembly [test path]. Could not get bytes from loader AppDomain
The second (after I try to run NCover) says it 'Could not load config' for the test dll.
I copied the 4 XML config file (Bolt.ext.config, Bolt.Extension2008.dll.config, NCover.exe.config, ncover.axplorer.exe.config) from one of my team members, so I'm pretty sure that I have my config correct.
Has anyone else experience this/have any suggestions? Help would be greatly appreciated!
Further information:
When I hover over the grayed out test dll in the bolt test panel, I get the following error:
Assembly is not loaded. Select and run to build and load this assembly
I was looking at this post, but it doesn't seem like any of the solutions are working for me...
After working with some of the other developers in my office, we discovered the issue was with the NCover version. For our tests to run, we needed to use NCover v5.0. Neither v5.1 or v5.2 would work with our setup. Not sure what changed in v5.1 that wouldn't let it find the tests, but I'm glad it's working now :)
I've recently upgraded from Java 6 to Java 7, and changed the Grails version accordingly to 2.3.8. Everything compiles and runs fine from the command line.
But I'm finding my version of GGTS (3.5.1.RELEASE) won't run unit tests from within the editor. I get the error:
java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal
I've tried completely importing the project from scratch - no joy.
The problem applies only to Grails-specific tests in GGTS, not when I run them from the command line. It happens during the Grails initialisation registerBeans() call. Which is pulled in by the #TestFor annotation (no annotation, no problem).
Looking at other error reports with the same error, I see this seems to be something to do with versions of xml-apis. I've tried putting
compile('xml-apis:xml-apis:2.0.2')
in the grails.project.dependency.resolution ... dependencies section of BuildConfig.groovy, but it has no effect.
Any suggestions what I might do instead?
Charles
My Grails guru suggested simply moving to IntelliJ - a good, if slightly costly, approach.
But to my frustration I found a different, but similar, error in that environment too. I realised that IntelliJ imports the Eclipse editor settings for the project.
So the solution turned out to be to delete all the editor-specific files for the project, and regenerate it from the Groovy/Grails sources alone.
Charles
I am running VS 2012 (Version 11.0.61030.00 Update 4). I created a project to run unit tests which had been working 100%. I have 2 test settings profiles. One for running tests local (still works fine) and another for running test remotely (using a test controller and test agents). All tests worked back in Feb. 2014. I have not run them until today. I receive the following error in the Visual Studio output window for tests:
Cannot discover test extensions installed by NuGet. The NuGet service is not
available. Tests may not be found due to missing test adapter extensions. The
connection to the controller was lost.
As far as I know I never configured NuGet in the first place. At this point, I don't really want to use it until I thoroughly research the technology. It is quite possible I updated the Visual Studio software between Feb and now, but I don't think so. Why do I have a sudden dependecy on NuGet?
What can I do to fix this? I suppose this could be a bogus message and my real problem is something else entirely, but hopefully someone else has seen this.
NOTE: connection is not an issue. I have a solid drive mapping from VS2012 machine to Test Controller. Tests do not deploy to controller or to test agent machines. Problem is not limited to Unit Test project. I have a CUITest project with the same issue, but let's stick to unit test project for this post.
thanks
The message I was seeing referring to NuGet had nothing to do with my issue. Yes, I would see this message during test execution, but I'm also seeing it during builds. The message was likely always there I just failed to notice it. My problem was actually tied to something else and since I could ignore the Nuget message, I focused more on the "connection to the controller was lost" message.
So now my issue: As stated I had a solid connection from VS2012 to the controller. However, you also need a connection from the controller back to the VS2012 machine. There was a connectivity issue in that direction due to my DHCP address changing (lease expired). So there was no code issue. It was an environment issue. The NuGet error was just a distracting waste of time.