Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting UseParentFQNForParametrizedTests via nunit.runsettings does not work #730

Closed
johnmwright opened this issue Mar 19, 2020 · 2 comments
Labels
closed:noresponse No response from reporter soon:closing Will be closed soon if no further response

Comments

@johnmwright
Copy link
Contributor

johnmwright commented Mar 19, 2020

I'm running Microsoft Visual Studio Enterprise 2019 (Version 16.5.0) with NUnit3TestAdapter v3.16.1.

In order to take advantage for the fixes from v3.16.0 from PR #668 , I've created a nunit.runsettings file as noted here that looks like this:

<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
   <NUnit>
     <UseParentFQNForParametrizedTests>True</UseParentFQNForParametrizedTests>
     <UseNUnitIdforTestCaseId>True</UseNUnitIdforTestCaseId>
   </NUnit>  
</RunSettings>

I've attempted placing the file in the following locations:

  • The solution folder
  • The test project folder
  • The test project bin (output) folder

However, in none of those cases does the applicable configuration option get set, thus the bug fixed by #668 continues to haunt me.

Can you provide guidance on how to properly override those two settings?

@OsirisTerje
Copy link
Member

It doesn't matter where the file is placed. You need to add the file location (path+name) to whatever test runner you're using. Which one is that ?

@OsirisTerje
Copy link
Member

Sorry, read your post too fast.
Do you have VS set to find the runsettings automatically?
Have you tried to set it manually? Then you set the direct path/location and it will find it.
You can add one more NUnit setting, e.g. verbosity, so that you can verify it is being used.

Also be aware that your case can be one of them not fixed.

@OsirisTerje OsirisTerje added the soon:closing Will be closed soon if no further response label Apr 20, 2020
@OsirisTerje OsirisTerje added the closed:noresponse No response from reporter label May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed:noresponse No response from reporter soon:closing Will be closed soon if no further response
Projects
None yet
Development

No branches or pull requests

2 participants