Get Executing Path of C# application when using nunit with Jenkins

» chash » Get Executing Path of C# application when using nunit with Jenkins

By : Kristóf Kosztyó

Date : November 25 2020, 07:22 PM

seems to work fine I use Jenkins, for building, unit testing, and publishing a windows application in c#. While executing test cases using nunit-console.exe, some of them needs Application.Executing Path for completing the test case. And it returns, nunit-console.exe path as result. Hence these test cases getting failed. ( What i need here is C# application executing path) How can i solve this issue.

code :

Share :

NUnit Test on Jenkins fail (nunit xml result file is empty )

By : Felipe Vera

Date : March 29 2020, 07:55 AM

it should still fix some issue The problem was as followed:
The unit tests are executed via the powershell script. The powershell start process does not wait untill the process has finished. This causes the problem that a child process is not finished.

Executing NUnit tests through a Windows Form application with NUnit Engine

By : Md Anowar hosen

Date : March 29 2020, 07:55 AM

With these it helps I'm trying to execute NUnit tests through a Windows Form application with NUnit Engine, but I don't understand how to set the path for the DLL where my tests are (I have already included the DLL in the references). When I click a button, I want the tests to start; however, NUnit opens and then immediately closes without doing anything. Here's what I have: , I never got a real answer to this but I figured it out myself.

code :

private void ATF_Main_Load(object sender, EventArgs e)
    {
        // Add reference to tests DLL and load it here by name
        Assembly testAssembly = Assembly.Load("Program.Tests");
        package = new TestPackage(testAssembly.Location);
        package.AddSetting("Working Directory", Environment.CurrentDirectory);
    }

Jenkins build fails because it is looking for log path defined in logback.xml when executing junit test

By : Ahmed Hosni

Date : March 29 2020, 07:55 AM

may help you . I resolved the issue by using @TestPropertySource(properties = "logging.config=classpath:logback.xml") where in the logback-spring.xml was ignored during Jenkins build.

NUnit and Continuous Integration with Jenkins: which NUnit-files are needed?

By : Bart Meuwis

Date : March 29 2020, 07:55 AM

I hope this helps . I have been using a slightly different approach to integrating NUnit with Visual Studio (C#, MSBuild) under Jenkins. The VS Solution contains several projects underneath it that build around 10 DLLs and 1 Application. The Visual Studio Solution does not invoke NUnit.
Sitting alongside the "application" code is a directory containing the test code. There is a Test solution that is built independently. It references the output of the application solution.