Ok, I see plenty of these errors around. I have tried everything I know to do and have yet to figure this out.

I am working on a development server running python 2.5 and Django 1.3. Django 1.3 was installed using python setup.py install after unpacking the tar.gz download.

All works well, I seldom have the need to run manage.py but am trying to use the new staticfiles app and am running into problems.

python manage.py collectstatic
Traceback (most recent call last):
  File "manage.py", line 2, in <module>
    from django.core.management import execute_manager
ImportError: No module named core.management

Ok, so I have PATH issue.

From I double check my site-packages directory.

python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"
/usr/lib/python2.5/site-packages

Ok, let's check out what I have, echo $PYTHON_PATH was empty, so I set it

export PYTHON_PATH=/usr/lib/python2.5/site-packages/django

Still no luck. Lets check what sys.path has to say

['', '/usr/lib/python2.5', '/usr/lib/python2.5/plat-linux2', '/usr/lib/python2.5/lib-tk', '/usr/lib/python2.5/lib-dynload', '/usr/local/lib/python2.5/site-packages', '/usr/lib/python2.5/site-packages', '/usr/lib/python2.5/site-packages/PIL', '/usr/lib/python2.5/site-packages/django', '/var/lib/python-support/python2.5']

path is there, I even created /usr/lib/python2.5/site-packages/django.pth with contents

cat /usr/lib/python2.5/site-packages/django.pth 
/usr/lib/python2.5/site-packages/django/

Anyone got an clues to what is going on here?

I found a symlink further up the path that was getting in the way, but no on to a new error.

python manage.py collectstatic
Traceback (most recent call last):
  File "manage.py", line 14, in <module>
    execute_manager(settings)
  File "/usr/lib/python2.5/site-packages/django/core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/usr/lib/python2.5/site-packages/django/core/management/__init__.py", line 349, in execute
    version=get_version(),
  File "/usr/lib/python2.5/site-packages/django/__init__.py", line 12, in get_version
    from django.utils.version import get_svn_revision
ImportError: No module named utils.version

I also tried creating a new project to see if there were any issues there and get the same utils.version error.

Side node: Unode from

django helped me a bit, set up virtualenv on same machine and got past the errors so still not sure what is up with this actual install here, but it seems to not be in the django projects but in the django/python install.

I checked the references and the test project has the reference to main project. Any idea why the test are not running or saying that they were inconclusive?

Edit 1:

I saw a post here and changed my test's setting's default processor architecture to X64 but it still doesn't work.

asked Aug 19, 2013 at 10:03

8

Just in case none of the above options worked for anyone I fixed my instance of this error by noticing a corrupt entry in my App.Config due to a missing nuget package in the test project.

answered Jan 27, 2014 at 16:59

Chris PaceyChris Pacey

1,7872 gold badges14 silver badges11 bronze badges

9

For me it was rather frustrating, but I've found solution for my case at least:

If your TestMethod is async, it cannot be void. It MUST return Task.

Hope it helps someone :)

answered Mar 15, 2016 at 15:59

0

I had the same issue with resharper and I corrected this error by changing an option:

Resharper => Options => Tools => Unit Testing

I just had to uncheck the option "Shadow-copy assemblies being tested"

answered Nov 27, 2013 at 14:32

Elias PlatekElias Platek

1,0841 gold badge9 silver badges16 bronze badges

4

It was a Resharper issue. In Resharper options->Tools->MSTEST, I unchecked the Use Legacy Runner and now it works.

Carra

17.9k7 gold badges63 silver badges75 bronze badges

answered Aug 21, 2013 at 11:46

CybercopCybercop

8,57521 gold badges75 silver badges135 bronze badges

3

I faced this problem in vs 2017 update 3 with Resharper Ultimate 2017.2

Restart vs or restart machine can't help.

I resolved the problem by clearing the Cache as follows:

    Resharper ->options-> Environment ->click the button 'Clear caches'

Update:

There is a button "error" (I find in Resharper 2018) in the upper right corner of the test window.

If you click the error button, it shows an error message that may help in resolving the problem.

To track the root of the problem, run Visual Studio in log mode. In vs 2017, Run the command:

      devenv /ReSharper.LogFile C:\temp\log\test_log.txt /ReSharper.LogLevel Verbose

Run the test.

Review the log file test_log.txt and search for 'error' in the file.

The log file is a great help to find the error that you can resolve or you can send the issue with the log file to the technical support team of Resharper.

answered Aug 18, 2018 at 23:33

M.HassanM.Hassan

10.5k5 gold badges66 silver badges86 bronze badges

2

For me, simply cleaning and rebuilding the solution fixed it.

answered Dec 19, 2013 at 22:50

Mike ChamberlainMike Chamberlain

40.4k28 gold badges110 silver badges159 bronze badges

1

I was having this problem, and it turned out to be the same as this problem over here. This answer solved the problem for me.

1. Uncheck "Only build startup projects and dependencies on Run" (Options -> Projects and Solutions -> Build and Run)

2. In Configuration Manager, make sure both the start-up project and the Test project have "Build" checked.

The second time I hit this issue, it was due to an ampersand in the filepath to the project where the tests reside. It works fine with ReSharper's test runner, but not dotCover's. Remove the ampersand from the filepath.

This is a confirmed bug with dotCover.

answered Apr 5, 2015 at 15:29

RubberDuckRubberDuck

12.2k5 gold badges51 silver badges95 bronze badges

1

For me, the problem was a corrupt NUnit/ReSharper settings XML-file (due to an unexpected power shortage).

To identify the error I started Visual Studio with this command:

devenv.exe /ReSharper.LogFile C:\temp\resharper.log /ReSharper.LogLevel Verbose

Examining the file revealed the following exception:

09:45:31.894 |W| UnitTestLaunch                | System.ApplicationException: Error loading settings file
System.ApplicationException: Error loading settings file ---> System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.Load(String filename)
   at NUnit.Engine.Internal.SettingsStore.LoadSettings()
   --- End of inner exception stack trace ---
   at NUnit.Engine.Internal.SettingsStore.LoadSettings()
   at NUnit.Engine.Services.SettingsService.StartService()
   at NUnit.Engine.Services.ServiceManager.StartServices()
   at NUnit.Engine.TestEngine.Initialize()
   at NUnit.Engine.TestEngine.GetRunner(TestPackage package)
   at JetBrains.ReSharper.UnitTestRunner.nUnit30.BuiltInNUnitRunner.<>c__DisplayClass1.<RunTests>b__0()
   at JetBrains.ReSharper.UnitTestRunner.nUnit30.BuiltInNUnitRunner.WithExtensiveErrorHandling(IRemoteTaskServer server, Action action)

Note that this is NOT the test project's app.config!

A quick googling around identified the following file as the culprit:

%LOCALAPPDATA%\NUnit\Nunit30Settings.xml

It existed, but was empty. Deleting it and restarting Visual Studio solved the problem.

(Using Visual Studio Professional 2017 v15.3.5 and ReSharper 2017.2.1).

answered Sep 28, 2017 at 8:01

ReyhnReyhn

1,0061 gold badge12 silver badges22 bronze badges

0

My problem was that I had only installed NUnit with nuget. I hadn't installed NUnit3TestAdapter which was also required.

Install-Package NUnit3TestAdapter

answered May 2, 2018 at 15:43

Mike OlundMike Olund

4295 silver badges6 bronze badges

1

I just fixed this issue as well. However, none of the solutions in this thread worked. Here's what I did:

Since R# wasn't giving any detail about why things were failing, I decided to try the built-in VS2013 test runner. It experienced the exact same behavior where none of the tests ran. However, looking in the Output window, I finally had an error message:

An exception occurred while invoking executor 'executor://mstestadapter/v1': Object reference not set to an instance of an object.

This led me to another thread on SO with a solution. Believe me, I would have NEVER guessed what the issue was.

I had recently made a few changes to the AssemblyInfo.cs file while creating a NuGet package. One of the changes including specifying an assembly culture value of "en".

I changed this:

[assembly: AssemblyCulture("")] 

to this:

[assembly: AssemblyCulture("en")]`. 

That was it! That's what inexplicably broke my unit tests. I still don't understand why, however. But at least things are working again. After I reverted this change (i.e. set the culture back to ""), my tests began running again.

Hope that helps somebody out there.

Matthew

1,6601 gold badge15 silver badges19 bronze badges

answered Mar 18, 2014 at 15:09

mikesigsmikesigs

10.7k3 gold badges34 silver badges41 bronze badges

2

In my case i got this error because of 'Release' mode where build of UnitTests project was simply switched off. Switching back to 'Debug' mode fixed it.

It's really surprising that ReSharper cannot say anything in case it cannot find UnitTests library at all. Seriously, it's a shame;)

Hope it will help somebody

answered Jul 21, 2015 at 20:11

RR-FireballRR-Fireball

2403 silver badges10 bronze badges

In my case

    Resharper ->options-> Environment ->click the button 'Clear caches'

0 methods were just

    Resharper ->options-> Environment ->click the button 'Clear caches'

1. S-h-a-m-e

answered Jan 28, 2016 at 22:36

pkuderovpkuderov

3,5112 gold badges29 silver badges46 bronze badges

1

This error occurred with Visual Studio 2017 and resharper version 2018.2.3 but the fix applies to Visual Studio 2019 versions to.

The fix, to get tests working in Resharper, was simply to update to the latest version of Resharper (2019.2.1) at the time of writing.

answered Aug 29, 2019 at 14:30

navarqnavarq

1,1552 gold badges15 silver badges21 bronze badges

In my case it was a mistake i did while copying the connectionstring in the app.config.. I had put it inside the configSections tag!

Took me a while to realize that... thanks VS intellisense though.. or was it resharper?

answered Apr 12, 2014 at 13:45

Kcats WolfrevoKcats Wolfrevo

8031 gold badge11 silver badges15 bronze badges

4

I had similiar issue. VS 2010, c# CLR 2 Nunit 2.5.7 , just build > clean solution from VS helped to resolve this issue

answered Feb 4, 2014 at 21:53

In my case I created an async test method which returned

    Resharper ->options-> Environment ->click the button 'Clear caches'

2. Returning of

    Resharper ->options-> Environment ->click the button 'Clear caches'

3 instead of

    Resharper ->options-> Environment ->click the button 'Clear caches'

2 solved the issue.

answered Nov 10, 2015 at 20:52

NeshtaNeshta

2,6452 gold badges27 silver badges45 bronze badges

In my case, all tests within some test projects within a solution started not running after I added new projects. Using VS 2017 with ReSharper 2017.1.2 here.

First of all, make sure you're not wasting time assuming that your issue is ReSharper related. It is easy to assume that there's something wrong with ReSharper if you use its unit testing features including Unit Test Explorer. Open up Visual Studio's Test Explorer under the Test menu and try Run All". The added advantage of doing this is that the output window will show an error message that might point you in the right direction. If you notice that the same set of test are not run, then it is safe to assume that the issue is with Visual Studio and not ReSharper.

I ended up deleting and re-adding one of the Active solution platform, Any CPU, in Configuration Manager. By doing so, after saving my changes and reopening the solution, all tests started running again.

I believe there was an unexpected configuration entry in the solution file when I added new projects and by using recreating one of the platforms, it corrected itself. I tried diffing but it was difficult to tell what had changed to cause the issue.

Neo

4,2656 gold badges55 silver badges77 bronze badges

answered Jun 2, 2017 at 19:06

wonsterwonster

7461 gold badge9 silver badges11 bronze badges

1

Have you added any DLL dependency recently? ... like me

I just ran into the same issue and it was very exasperating not to get any clue in the test output window or elsewhere practical.

The cause was extremely stupid: I just added the day before dependency to an additional external DLL in a sub-project, and the main project App indeed built and ran correctly after the change. But my unit tests are in a sister project to the main app, and thus had too the dependency on this changed sub project where the DLL was invoked... yet, the runtime location of the test project is not that of the main App! So changing the build to do copying of the missing DLL into the test runtime directory fixed the problem.

answered Sep 15, 2014 at 8:30

Bernard HauzeurBernard Hauzeur

2,3271 gold badge18 silver badges26 bronze badges

I am using VS2013, ReSharper 9.1 with MSpec extension from ReSharper and Moq. I experienced the same "inconclusive" error.

It turned out the one of my Mock's from Moq was not initialized, only declared. Ones initialized all tests ran again.

answered May 6, 2015 at 9:54

In my case my test method was private I changed it to public and it worked.

answered Apr 21, 2016 at 14:56

For those who are experiencing this issue for my test project

    Resharper ->options-> Environment ->click the button 'Clear caches'

5 in the

    Resharper ->options-> Environment ->click the button 'Clear caches'

6. I also had this bug using

    Resharper ->options-> Environment ->click the button 'Clear caches'

7 - there is a bug I posted.

JetBrains advised to create a new test project from scratch to reproduce it. When I did that and got tests working OK, I found the reason causing the issue:

• Remove this from your

  Resharper ->options-> Environment ->click the button 'Clear caches'  
  

  8 file:

• Resharper ->options-> Environment ->click the button 'Clear caches'  
  

  9"

When I did that - tests started working fine.

answered Sep 7, 2017 at 15:45

Dmitry PavlovDmitry Pavlov

31.2k8 gold badges99 silver badges123 bronze badges

2

For who are in rush for test execution, I had to use VS 2017 test explorer to run tests;

answered Feb 16, 2018 at 20:38

Teoman shipahiTeoman shipahi

47.8k16 gold badges136 silver badges161 bronze badges

0

I'm was having the same problem to run any test using NUnit framework. "Inconclusive: Test not run" Visual Studio 2017 15.5.6

ReSharper Ultimate 2017.3.3 Build 111.0.20180302.65130

SOLVED Adding project dependency to Microsoft.NET.Test.Sdk

answered Mar 12, 2018 at 11:49

2

I'm using VS2010, NUnit 2.6.3 (although internally ReSharper says it's using 2.6.2?), ReSharper 7.7.1 & NCrunch 2.5.0.12 and was running into the same "...test is inconclusive..." thing with NUnit, but NCrunch said everything was fine. For most of today NUnit & NCrunch were in sync agreeing about which tests were happy and which needed refactoring, then something happened which I still don't understand, and for a while NCrunch said I had failing tests (but stepping through them showed them to pass), then decided they were all working, and NUnit started complaining about all my tests except one with the same message "..test is inconclusive..." which I was again able to single step through to a pass even though NUnit continued to show it as "inconclusive").

I tried several of the suggestions above to no avail, and finally just closed VS2010 & reopened the solution. Voila, now all my tests are happy again, and NCrunch & NUnit are reporting the same results again. Unfortunately I have no idea what changed to cause them to go out of sync, but closing & reopening VS2010 seems to have fixed it.

Maybe someone else will run into this and be able to use this simple (if ultimately unsatisfying since you don't know what the real fix is) solution.

answered Mar 24, 2014 at 22:05

delliottgdelliottg

3,9703 gold badges38 silver badges52 bronze badges

I had this same issue. The culprit was an external reference not being compatible with my project build settings. To resolve, I right clicked on the project->properties->build->Platform Target-> change from Any CPU to x86.

The particular *.dll that I was working with was System.Data.SQLite. That particular *.dll is hardcoded for 32 bit operation. The "Any CPU" setting attempted to load it as 64 bit.

answered Jun 5, 2015 at 16:31

sapbucketsapbucket

6,87516 gold badges58 silver badges94 bronze badges

1

My solution:

NUnit 3.2.0 has some issues with Resharper - downgrade to 2.6.4:

update-package nunit -version 2.6.4

answered Apr 6, 2016 at 4:41

David McEleneyDavid McEleney

3,4731 gold badge26 silver badges32 bronze badges

0

Caused by missing (not corrupt) App.Config file. Adding new (Add -> New Item... -> Application Configuration File) fixed it.

answered Jul 1, 2016 at 13:43

0

I had the same problem.It was related to compatibility version between NUnit 3.5 and Resharper 9.2,since it was solved by downgrading from NUnit 3.5 to 2.6.4. It worked for me. good luck.

answered Dec 26, 2016 at 8:02

Ali Gol GolAli Gol Gol

7757 silver badges14 bronze badges

2

If you are using

      devenv /ReSharper.LogFile C:\temp\log\test_log.txt /ReSharper.LogLevel Verbose

0, I solved the issue installing

      devenv /ReSharper.LogFile C:\temp\log\test_log.txt /ReSharper.LogLevel Verbose

1 package. (currently using

      devenv /ReSharper.LogFile C:\temp\log\test_log.txt /ReSharper.LogLevel Verbose

2 and

      devenv /ReSharper.LogFile C:\temp\log\test_log.txt /ReSharper.LogLevel Verbose

3)

answered Nov 9, 2017 at 9:36

I had the exact same problem, no tests were run in my test-project. As it happend I had the wrong configuration selected when running the tests. Changing it back to Debug fixed the problems.