@tannergooding
[Platform("Win")] sounds correct, but the error sounds like you are using an older version of NUnit - before version 3.13 - see e.g. nunit/nunit#3565 for some more information
Hey all, I looking for some help. I'm using
<PackageVersion Include="NUnit" Version="3.13.1" />
<PackageVersion Include="NUnit.Analyzers" Version="3.0.0" />
<PackageVersion Include="NUnit3TestAdapter" Version="3.17.0" />
<PackageVersion Include="Microsoft.NET.Test.Sdk" Version="16.8.3" />When I run dotnet test in my the root folder of my solution, my tests are found and run successfully:
D:\dvlp\cdp\MyProductionProject [develop ≡ +0 ~1 -0 !]> dotnet test
Determining projects to restore...
Restored D:\dvlp\cdp\MyProductionProject\src\MyProductionProject\MyProductionProject.csproj (in 1.82 sec).
Restored D:\dvlp\cdp\MyProductionProject\tests\MyProductionProject.Unittests\MyProductionProject.UnitTests.csproj (in 1.82 sec).
Restored D:\dvlp\cdp\MyProductionProject\tests\MyProductionProject.Functionaltests\MyProductionProject.Functionaltests.csproj (in 1.82 sec).
2 of 5 projects are up-to-date for restore.
MyProductionProject.Interface -> D:\dvlp\cdp\MyProductionProject\src\MyProductionProject.Interface\bin\Debug\netstandard2.0\MyProductionProject.Interface.dll
MyProductionProject.Core -> D:\dvlp\cdp\MyProductionProject\src\MyProductionProject.Core\bin\Debug\netstandard2.0\MyProductionProject.Core.dll
MyProductionProject.UnitTests -> D:\dvlp\cdp\MyProductionProject\tests\MyProductionProject.Unittests\bin\Debug\net472\MyProductionProject.UnitTests.dll
Test run for D:\dvlp\cdp\MyProductionProject\tests\MyProductionProject.Unittests\bin\Debug\net472\MyProductionProject.UnitTests.dll (.NETFramework,Version=v4.7.2)
MyProductionProject -> D:\dvlp\cdp\MyProductionProject\src\MyProductionProject\bin\Debug\net472\MyProductionProject.exe
Microsoft (R) Test Execution Command Line Tool Version 16.8.3
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
MyProductionProject.Functionaltests -> D:\dvlp\cdp\MyProductionProject\tests\MyProductionProject.Functionaltests\bin\Debug\net472\MyProductionProject.Functionaltests.dll
Test run for D:\dvlp\cdp\MyProductionProject\tests\MyProductionProject.Functionaltests\bin\Debug\net472\MyProductionProject.Functionaltests.dll (.NETFramework,Version=v4.7.2)
Microsoft (R) Test Execution Command Line Tool Version 16.8.3
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Passed! - Failed: 0, Passed: 36, Skipped: 0, Total: 36, Duration: 869 ms - MyProductionProject.UnitTests.dll (net472)
Passed! - Failed: 0, Passed: 12, Skipped: 0, Total: 12, Duration: 16 s - MyProductionProject.Functionaltests.dll (net472)however, trying to run the tests project at a time doesn't work
D:\dvlp\cdp\MyProductionProject [develop ↑2]> dotnet test Tests\MyProductionProject.UnitTests\MyProductionProject.UnitTests.csproj --no-build
Test run for D:\dvlp\cdp\MyProductionProject\Tests\MyProductionProject.UnitTests\bin\net472\MyProductionProject.UnitTests.dll (.NETFramework,Version=v4.7.2)
Microsoft (R) Test Execution Command Line Tool Version 16.8.3
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
No test is available in D:\dvlp\cdp\MyProductionProject\Tests\MyProductionProject.UnitTests\bin\net472\MyProductionProject.UnitTests.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>.any ideas? i'm stuck with this crap for a day now, probably something dumb i'm missing
if i run a specific test project it doesn't run... which make me mad, cuz the CI is running the test projects 1 by 1, while I run them all together on my machine :D
so there is something missing
if you create a new test project using dotnet new unit, and then try to run that, does that work ?
https://pastebin.com/jAYY8jym there is a trace here from my build and both test runs... its a bit long I preferred to paste it outside so to not spam
ok it seems like i've found it. once i began looking at the paths side by side i found that the dotnet test on the solution will generate paths with different cases, based on the paths in the sln file. which would work... for some reason, targeting the csproj directly (like our CI) would do wasn't working well, probably because the build paths and dll names were a bit different
Hello! Is there any way of doing the following cleanly? I want to add multiple constraints on some Property(), but I'm not sure on how to do that. My apologies if this isn't the right place for asking this...
class Two
{
public string C { get; set; }
public string D { get; set; }
}
class One
{
public string A { get; set; }
public Two B { get; set; }
}
[Test]
public void MyTest()
{
// Imagine that this is returned by some function
var result = new One {A = "a", B = new Two {C = "c", D = "d"}};
Assert.That(result, Has.Property("A").EqualTo("a")
// Constraints on result.B.*
.And.Property("B").Property("C").EqualTo("c")
.And.Property("B").Property("D").EqualTo("d"));
}
One existing way to do this is to make the test method nonvirtual in the base class and have it call derived impls.
1 reply
@utybo Constraint syntax doesn't really let you form a tree structure like that. I'd use two assert statements.
3 replies
Hi I have some non-test code that creates an AppDomain and loads a class, it never references NUnit in any way. Now I am testing this code using NUnit and somehow when I create the very same class from the very same non-testcode binary it wants to load NUnit.Framework on that AppDomain. Does NUnit 'inject' itself in someway in an AppDomain, if so, why? This is causing issues now as it cannot find the binary and I don't want 'load NUnit.Framework' code in non-test code. Is there a way around this that it doesn't do that for certain domains?
2 replies
Currently I use NUnit with VS Adapter in Visual studio - with about 10k tests which works quite nice
I only some way to categorize errors
Is there some way to group by exception?
no executed / pass and fail seem to be insufficient
Hello. I have a parametric fixture, and I want to use the parameter value to further generate parameters for a particular test within that fixture. Is this possible somehow? I have a feeling I would need to provide my own ITestBuilder, but I'm not sure if it's possible for me to access the fixture parameters from that point.
with the testcase source you are free to create what data you like...
anyway, I found a solution - inside ITestBuilder,
suite.Arguments actually does contain the parameters for my fixture, so I can use it to generate my test cases
Hidiho, what is the proper way to provide data to for tests? Until now i copied data outside of the tests in scripts, the problem is though that this makes working in Visual Studio a bit cumbersome. So i thought to do the copying in the tests now, this does not seem to work as intended though since the TestCaseSources are evaluated earlier than all the SetUp attributed Methods. Is there any way to make this work properly or should i try to find another solution?
@b0urb4k1 Not sure what is the problem, first TestCaseSources evaluated before SetUp - not really, but you probably have something static there, anyway, it should not affect your tests. Whether you have your test data in seperate files or included with the source code, should not matter. You can look at the test project and the acceptance test project in the adapter for one way of doing it. It could also help if you could show some code to exemplify what is your problem, easier for us to help too :-)
What i want to do is to copy some files that are used to build the TestCaseSources. The TestCaseSource iterates and searches for files that should previously been copied. I read somewhere that the TestCases are used to build the actually run tests before the setup methods are called, which would explain the behaviour i see, that is am empty folder. So what i did now is to copy the files in the static property's get method, which works but is of course kind of sucky.
You can use a OneTimeSetup attributed method to do that, if all your tests are in the same test class. If they are over m,ultiple classes, you can use a SetupFixture for the same purpose, and place that at global level, so that it is at assembly level. It will run before any tests are executed. See details here: https://docs.nunit.org/articles/nunit/writing-tests/attributes/setupfixture.html
Well at least the OneTimeSetup on the actual test did not work, that is what i had.
I will check if it works with the fixture though tomorrow.
Still now 100% ideal, since this also would copy data that is not used if you run it from the VS Test Explorer. With a single test that is.
Cool.... if the OneTimeSetup didnt work, there is something you do in the file loading - but anyway , the setupfixture should do it for you. TestCaseSources are statics, so they can fool you if you access them too early. They should be doing things in a lazy manner, not in the ctor.
I also might try to use the proposed static constructor.
Oh now that is nifty :) i also could do the lazy thing and just copy the file when the test gets instanciated ... :)
The code i wrote to sync the server and local directory is split up in yielding commands that need to be executed in order to do the sync and an interpreter, so i think i should be able to enumerate the query in the TestCaseSource and wrap them in a Func with the deleted files calling Assert.Ignore