Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 18:47
    jnm2 edited #3516
  • 18:47
    jnm2 edited #3516
  • 18:46
    jnm2 edited #3516
  • 18:43
    jnm2 edited #3516
  • 18:37
    jnm2 edited #3516
  • 18:36
    jnm2 opened #3516
  • 18:36
    jnm2 labeled #3516
  • 14:54
    manoharsingh2110 commented #733
  • 14:49
    manoharsingh2110 commented #733
  • 13:13
    manoharsingh2110 commented #733
  • 02:37
    CharliePoole commented #733
  • Mar 28 17:34
    ChrisMaddock commented #733
  • Mar 28 17:34
    ChrisMaddock commented #733
  • Mar 28 17:33
    ChrisMaddock unlabeled #733
  • Mar 28 17:33
    ChrisMaddock assigned #733
  • Mar 28 17:07
    manoharsingh2110 commented #733
  • Mar 28 00:46
    jnm2 closed #223
  • Mar 28 00:46
    jnm2 commented #223
  • Mar 27 21:06
    jnm2 commented #3493
  • Mar 27 21:06
    Build #6630 passed
Mikkel Nylander Bundgaard
@mikkelbu

I'm able to run GitLink locally, but the output is difficult to compare. However, on the buildserver this line looks strange (line 930)

File "c:\users\vssadministrator\appdata\local\temp\.netframework,version=v4.0.assemblyattributes.cs" missing or changed since the PDB was compiled.

all other paths are

File "d:\a\1\s\src\...
Mikkel Nylander Bundgaard
@mikkelbu
I think one possibility is to use BaseDir - see https://cakebuild.net/api/Cake.Common.Tools.GitLink/GitLink3Settings/ - to filter away this file. But why it is necessary now I don't know. The issue could be related to this issue
https://developercommunity.visualstudio.com/content/problem/859013/sourcelinktesttargets-error.html
Mikkel Nylander Bundgaard
@mikkelbu
I've made a PR that makes the Package target work again - nunit/nunit#3451. But as far as I can tell the reference to .netframework,version=v4.0.assemblyattributes.cs is still in the PDB file, and I'm unsure about the consequences of this. @jnm2 do you know if it will be a problem that our pdb files mentions unknown files (or more precisely temp-files)?
avilv
@avilv
@mikkelbu thanks - ill ignore the error for now
avilv
@avilv
hmm a quick question, is there a way to prevent the VS test runner from using the nunit.framework's code when debugging nunit source code ? i mean the actual runner itself.. i know its confusing o_O
Terje Sandstrom
@OsirisTerje
@preethamrajk Hi! Sorry for noticing this a bit late. But if you want your issue https://developercommunity.visualstudio.com/content/problem/812548/multiple-automated-test-cases-mapped-to-single-tes.html handled in NUnit you should raise the issue there. I downloaded your repro project, but it didnt contain anything but the template generated test case. When you raise the issue, please add a working repro :-)
Ghost
@ghost~5e0f6fbcd73408ce4fd5a4da
Hey! I am new to NUnit and trying to create a test project for my UWP desktop application. Can you please let me know if NUnit supports UWP desktop applications and if there are any available examples online for reference because I could not find any.
Terje Sandstrom
@OsirisTerje
@milindmathur04_gitlab The adapter currently doesn't suppert UWP, see nunit/nunit3-vs-adapter#322 . Now also wondering whether we will, given "information" like this: https://www.theverge.com/2019/5/30/18645609/microsofts-universal-windows-app-dead-microsoft-store-windows-store . Microsoft response seems more optimistic https://www.windowscentral.com/microsoft-uwp-not-dead-evolved, but there doesn't seem to be any real demand either for UWP support. Any reason you want to use it ?
Terje Sandstrom
@OsirisTerje
Resharper have issues with the fixed FQN changes in NUnit3TestAdapter version 3.16. See https://youtrack.jetbrains.com/issue/RSRP-477651 This affects parametrized tests with custom names.
Marius Morar
@marius02
@all is there a way to add a context-menu with Run Tests option for any windows folder that contains Nunit tests ? any hints ?
Terje Sandstrom
@OsirisTerje
@marius02 This one is pretty close I think: https://stackoverflow.com/questions/20449316/how-add-context-menu-item-to-windows-explorer-for-folders . It solves the context menu, and you can run dotnet test from that one, but if you want to figure out if the assemblies contains test, and nunit tests in particular, you need some convention for your tests.
molszews
@molszews
just tested 3.16.1-dev-01248, it solves filtering issue, any plans for public release? @OsirisTerje
molszews
@molszews
Ah, Saturday, thanks!
Terje Sandstrom
@OsirisTerje
NUnit3TestAdapter version 3.16.1 is released now on nuget.org and VSIX on Visual Studio marketplace. See all issues resolved and Release notes for details.
Lars Nielsen
@lars-nielsen

Hi guys

Is there any way to instruct the nunit3-vs-adapter to place testresults.xml in the "TestsResults/{guid}" folder that is being generated by the "dotnet test" command.

See https://gist.github.com/lars-nielsen/38b9501de994ac928e9122853ca5113a if my question is unclear

Terje Sandstrom
@OsirisTerje
@lars-nielsen Have you tried setting the TestOutputXml in a runsettings file? See https://github.com/nunit/docs/wiki/Tips-And-Tricks#TestOutputXml
We should add a default for dotnet test though....
Terje Sandstrom
@OsirisTerje
And, I see that grabbing that guid could be an issue.... Not sure what generates that one, or if it is accessible to us
Lars Nielsen
@lars-nielsen
@OsirisTerje Yep, tried that - The guid is the issue. Im guessing its being generated by the TestPlatform as Coverlet.Collector places the coverage in the folder, but i have no deeper knowledge of what and how that part is managed
Terje Sandstrom
@OsirisTerje
@lars-nielsen Thanks, I'll check with MS
Sam Harwell
@sharwell
@jnm2 any idea when source debugging will work with NUnit?
I saw some issues you filed about it and was expecting it to work when I updated to 3.12.1, but it still says it can't find the symbol packages on either the NuGet or SymbolSource feeds
Mikkel Nylander Bundgaard
@mikkelbu
@sharwell
Have you followed the description in https://github.com/nunit/docs/wiki/Debugger-Source-Stepping ?
Sam Harwell
@sharwell
Yes, the workaround does not work though. Only manually copying the file works. I would recommend changing the PDB to embedded instead of full, which eliminates the need to copy altogether.
neeth
@praneethdabest_twitter
Hello, I have Specflow Tests running in DOTNETCORE project. How may I set up the Command Line arguments to specify a test trait or a feature file. Thanks !
Nathan Johnstone
@nrjohnstone
hey guys, I've spent half of the day trying to get .NET core NUnit tests displaying their results in our TeamCity build server. Chased down a bunch of dead ends because the solution has morphed over the years depending on the combination of versions etc... Can anyone point me to somewhere that demonstrates how to setup "dotnet test" running NUnit .netcore test projects so the output will show in TC ?
ovebastiansen
@ovebastiansen
@nrjohnstone my guess is that to any help on this you need to supply some versions on tools you try to integrate. What is the TC version, dotnet core version, nunit and nunit adapter?
Terje Sandstrom
@OsirisTerje
@nrjohnstone Adding to what @ovebastiansen says, it would also help to see your current setup, the options you use for the commands. Just guessing wildly: you are using the --verbosity normal on dotnet test ? Not exactly TC, but you can have a look at the yaml files for the adapter, or take a look here if that helps: http://hermit.no/github-actions-including-how-to-build-net-framework-projects/#net-core-example
Lars Nielsen
@lars-nielsen

@nrjohnstone

Hi nathan,

We are using this logger and ofcourse NUnit3TestAdapter
https://github.com/spekt/nunit.testlogger

We then run our tests like this

dotnet test --logger:"nunit;LogFilePath=test-result.xml"

Hope this helps you in the right direction

Oleksandr Liakhevych
@Dreamescaper
As far as I remember, TeamCity automatically provides custom logger when you use dotnet test command with built-in configuration
image.png
Oleksandr Liakhevych
@Dreamescaper
Is there any place where to read about how Constraint Operators work?
I'm a bit confused with how that Right / Left Precedence works.
So for example, AndOperator has LeftPrecedence = RightPrecedence = 2. WithOperatorhas LeftPrecendence = 1, RightPrecedence = 4.
So in which cases using .With vs .And will give different results?
Chris Maddock
@ChrisMaddock
Not an area I'm familiar with - @jnm2 might be able to advise? :-)
ArcticStag
@ArcticStag
Hi All,
Does anyone know if I will be able to get this working with Visual Studio Code on Linux?
ovebastiansen
@ovebastiansen
I have a solution that is working in visual studio code, but on windows
But cannot see why it should not work on Linux
ArcticStag
@ArcticStag
@ovebastiansen Thanks
Julien
@LiohAu
The test explorer in visual studio mac is not detecting those attributes when set on a parent (abstract or not) class :
[TestFixture(Platform.iOS)]
[TestFixture(Platform.Android)]
any idea of what could be the issue ?
I know that was working on 2.6.4, is it different on 3.10 ?
Oleksandr Liakhevych
@Dreamescaper
Is there any way to execute certain action after each test fixture (class)? I tried to use TestActionAttribute on assembly, but this way I can only execute action after each test, or after all tests from assembly.
CharliePoole
@CharliePoole
@Dreamescaper That's what [OneTimeTearDown] in your fixture does.
Oleksandr Liakhevych
@Dreamescaper
@CharliePoole
Sure, but for that to work I need to define it for every class, or inherit all classes from some base class.
I would prefer to avoid that, that's why tried to solve it with assembly attributes
CharliePoole
@CharliePoole
Yes, a TestActionAttribute is currently the only way to specify the code once and then have it executed within the context of individual tests, if that's what you need. OTOH if you create an action attribute using ActionTargets.Suite, it should be run on each suite. You will have to check that the suite is actually a fixture in your code
CharliePoole
@CharliePoole
by examining the test argument that is passed to it.
Oleksandr Liakhevych
@Dreamescaper
@CharliePoole
Yeah, problem is that if I specify Suite - it is executed only once - after whole assembly.