and XSD: https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Schemas/TestResult.xsd
The total number of tests passing/failing/etc is cached in the XML for every parent element, if that helps.
I have created a project using NUNIT and installed few packages before creating the tests,which are : NUNIT, NUNIT3TESTADAPTER, SELENIUM.SUPPORT, SELENIUM.WEBDRIVER, SELENIUM.WEBDRIVER.CHROMEDRIVER.
To make the tests I had only url of a website which I used to create all the tests(successfully). Now I want to make an exe so I can give it to other people to run the exe file and see the test performing automatically through automation browser. but I do not know what to do and how to do. Any help would be appreciated.
I have searched alot on google but could not find an answer.
.\build.ps1 -Target Test from within the nunit folder (if you are on windows, there is a matching build.sh for linux). There is more information about building the source code in https://github.com/nunit/nunit/blob/master/BUILDING.md.
--where="cat == 213"
@karterfree_gitlab
I create instance of NUnit3FrameworkDriver from my current AppDomain and I want to use static properies of static classes. But. When I call those static mpoperies from test method, I got null as response.
When you call IFrameworkDriver.Load(string testAssemblyPath, IDictionary<string, object> settings);, you can pass test parameters through to the framework by adding the key FrameworkPackageSettings.TestParametersDictionary an IDictionary<string, string> value, e.g. new Dictionary<string, string> { ["MyParam"] = "MyValue" }
(See how it is decoded on the framework side: https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Api/DefaultTestAssemblyBuilder.cs#L139-L147)
TestContext.TestParameters["MyParam"] etc and deserialize from the string. https://github.com/nunit/docs/wiki/TestContext#testparameters
@oskarb
Nunit console 3.10. Any idea why some test failures are reported in the output from each test as each test finishes but failures from other test cases are only reported in the summary at the end after all tests have finished? Parallel execution not used. This causes Teamcity to not detect failures for the tests where the failure is only listed in the summary output.
I'm not sure. We'd appreciate if you have time to file at https://github.com/nunit/nunit-console/issues.
@OsirisTerje
@jnm2 Are you on top of the new process for .net foundation news ? Did you follow the slack discussions and the move to github ? And, for August, we should add the Adapter 3.14 release. Might manage 3.15 too.
No, I did not hear about this. I haven't had time to keep up with https://netfoundation.slack.com.
