blocks|key|660214|text|Jenkins确实有支持这一点的插件。确切的配置将在很大程度上取决于您的项目设置。有针对nUnit、MSBuild、nAnt等的特定插件。先从插件页面开始，但这不是很难弄清楚。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|660215|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Jenkins does have plugins that will support that. The exact configuration is going to depend quite a bit on your project setup. There are specific plugins for nUnit, MSBuild,nAnt etc. Start by looking at the plugins page, but it shouldn't be terribly difficult to figure out.

blocks|key|445888|text|这很好用，我以前已经设置过了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|445889|配置NUnit以将结果输出到XML文件，并配置NUnit+Jenkins+Plugin以使用此XML文件。结果将显示在仪表板上。|offset|length|445890|现在，如何调用NUnit取决于您。我们这样做的方式是:+Jenkins任务执行NAnt目标执行NUnit测试套件。|445891|您可以将Jenkins作业配置为在提交时运行和/或安排在特定时间运行。|445892|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/NUnit%2BPlugin^0|0|N|K|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

This works nicely, I've set this up before.

Configure NUnit to output the results to an XML file and configure the <a href="https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin" rel="noreferrer" title="NUnit Jenkins Plugin">NUnit Jenkins Plugin</a> to consume this XML file. The results will be available on the dashboard.

Now, how you invoke NUnit is up to you. The way we did it was:
Jenkins job executes NAnt target executes NUnit test suite.

You can configure Jenkins jobs to run on commit and/or scheduled at a certain time.

blocks|key|445926|text|我认为当构建没有通过时，最好失败，这样你就不会部署它。这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|445927|C:\YourNUnitDir\nunit-console.exe+C:\YourOutDir\YourLib.dll+/noshadow
if+defined+ERRORLEVEL+if+%25ERRORLEVEL%25+neq+0+goto+fail_build

::+any+other+command

:+fail_build
endlocal
exit+%25ERRORLEVEL%25|code-block|syntax|javascript|445928|参考：http://www.greengingerwine.com/index.php/2013/01/tip-check-errorlevel-in-your-post-build-steps-when-using-nunit/|offset|length|445929|entityMap|0|LINK|mutability|MUTABLE|url|http://www.greengingerwine.com/index.php/2013/01/tip-check-errorlevel-in-your-post-build-steps-when-using-nunit/^0|0|0|3|34|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I think it's better to fail the build when it doesn't pass so you don't deploy it. Do something like this:

<pre><code>C:\YourNUnitDir\nunit-console.exe C:\YourOutDir\YourLib.dll /noshadow
if defined ERRORLEVEL if %ERRORLEVEL% neq 0 goto fail_build

:: any other command

: fail_build
endlocal
exit %ERRORLEVEL%
</code></pre>

Reference: <a href="http://www.greengingerwine.com/index.php/2013/01/tip-check-errorlevel-in-your-post-build-steps-when-using-nunit/" rel="nofollow">http://www.greengingerwine.com/index.php/2013/01/tip-check-errorlevel-in-your-post-build-steps-when-using-nunit/</a>

blocks|key|446002|text|如果你不想硬编码你的单元测试项目，你最好写一个脚本来抓取你所有的单元测试项目的dll。我们用Powershell来做这件事，并遵循命名我们的单元测试项目的特定约定。下面是运行我们的单元测试的powershell文件的内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|446003|param(
[string]+$sourceDirectory+=+$env:WORKSPACE
,+$fileFilters+=+@("*.UnitTests.dll",+"*_UnitTests.dll",+"*UnitTests.dll")
,+[string]$filterText+=+"*\bin\Debug*"
)

#script+that+executes+all+unit+tests+available.
$nUnitLog+=+Join-Path+$sourceDirectory+"UnitTestResults.txt"
$nUnitErrorLog+=+Join-Path+$sourceDirectory+"UnitTestErrors.txt"

Write-Host+"Source:+$sourceDirectory"
Write-Host+"NUnit+Results:+$nUnitLog"
Write-Host+"NUnit+Error+Log:+$nUnitErrorLog"
Write-Host+"File+Filters:+$fileFilters"
Write-Host+"Filter+Text:+$filterText"

$cFiles+=+""
$nUnitExecutable+=+"C:\Program+Files+(x86)\NUnit+2.6.3\bin\nunit-console-x86.exe"

#+look+through+all+subdirectories+of+the+source+folder+and+get+any+unit+test+assemblies.+To+avoid+duplicates,+only+use+the+assemblies+in+the+Debug+folder
[array]$files+=+get-childitem+$sourceDirectory+-include+$fileFilters+-recurse+%7C+select+-expand+FullName+%7C+where+{$_+-like+$filterText}

foreach+($file+in+$files)
{
++++$cFiles+=+$cFiles+%2B+$file+%2B+"+"
}

#+set+all+arguments+and+execute+the+unit+console
$argumentList+=+@("$cFiles",+"/framework:net-4.5",+"/xml=UnitTestResults.xml")

$unitTestProcess+=+start-process+-filepath+$nUnitExecutable+-argumentlist+$argumentList+-wait+-nonewwindow+-passthru+-RedirectStandardOutput+$nUnitLog+-RedirectStandardError+$nUnitErrorLog

if+($unitTestProcess.ExitCode+-ne+0)
{
++++"Unit+Test+Process+Exit+Code:+"+%2B+$unitTestProcess.ExitCode
++++"See+$nUnitLog+for+more+information+or+$nUnitErrorLog+for+any+possible+errors."
++++"Errors+from+NUnit+Log+File+($nUnitLog):"
++++Get-Content+$nUnitLog+%7C+Write-Host
}

$exitCode+=+$unitTestProcess.ExitCode

exit+$exitCode|code-block|syntax|javascript|446004|该脚本足够健壮，我们可以在所有构建作业中重用它。如果您不喜欢NUnit控制台的完整路径，则可以始终将该位置放入path环境变量中。|446005|然后，我们将RunUnitTests.ps1文件放到构建服务器上，并使用以下批处理命令：|446006|powershell.exe+-file+"{full-path-to-script-direcory}\RunUnitTests.ps1"|446007|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If you don't want to hardcode your unit test projects, you are better off writing a script to grab all of your Unit Test project dll's. We do it with Powershell and follow a specific convention for naming our Unit Testing Projects. Here is the content of the powershell file that runs our unit tests: 

<pre><code>param(
[string] $sourceDirectory = $env:WORKSPACE
, $fileFilters = @("*.UnitTests.dll", "*_UnitTests.dll", "*UnitTests.dll")
, [string]$filterText = "*\bin\Debug*"
)

#script that executes all unit tests available.
$nUnitLog = Join-Path $sourceDirectory "UnitTestResults.txt"
$nUnitErrorLog = Join-Path $sourceDirectory "UnitTestErrors.txt"

Write-Host "Source: $sourceDirectory"
Write-Host "NUnit Results: $nUnitLog"
Write-Host "NUnit Error Log: $nUnitErrorLog"
Write-Host "File Filters: $fileFilters"
Write-Host "Filter Text: $filterText"

$cFiles = ""
$nUnitExecutable = "C:\Program Files (x86)\NUnit 2.6.3\bin\nunit-console-x86.exe"

# look through all subdirectories of the source folder and get any unit test assemblies. To avoid duplicates, only use the assemblies in the Debug folder
[array]$files = get-childitem $sourceDirectory -include $fileFilters -recurse | select -expand FullName | where {$_ -like $filterText}

foreach ($file in $files)
{
 $cFiles = $cFiles + $file + " "
}

# set all arguments and execute the unit console
$argumentList = @("$cFiles", "/framework:net-4.5", "/xml=UnitTestResults.xml")

$unitTestProcess = start-process -filepath $nUnitExecutable -argumentlist $argumentList -wait -nonewwindow -passthru -RedirectStandardOutput $nUnitLog -RedirectStandardError $nUnitErrorLog

if ($unitTestProcess.ExitCode -ne 0)
{
 "Unit Test Process Exit Code: " + $unitTestProcess.ExitCode
 "See $nUnitLog for more information or $nUnitErrorLog for any possible errors."
 "Errors from NUnit Log File ($nUnitLog):"
 Get-Content $nUnitLog | Write-Host
}

$exitCode = $unitTestProcess.ExitCode

exit $exitCode
</code></pre>

The script is robust enough that we are reusing for all of our build jobs. If you don't like the full path to NUnit console, you could always put that location in your PATH environment variable.

Then we put the RunUnitTests.ps1 file on our build server and use this batch command: 

<pre><code>powershell.exe -file "{full-path-to-script-direcory}\RunUnitTests.ps1"
</code></pre>

blocks|key|446095|text|对于.Net核心，添加“执行外壳”构建步骤和以下脚本就足够了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|446096|#!bash+-x

cd+$my_project_dir
rm+-rf+TestResults+++#+Remove+old+test+results.
dotnet+test+-l+trx|code-block|syntax|javascript|446097|之后，添加"Publish+MSTest+test+result+report“构建后操作，以使测试结果可见。|446098|默认测试报告路径应为**/*.trx，并将发布所有生成的.trx文件。|offset|length|style|CODE|446099|entityMap^0|0|0|0|A|8|S|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]|$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

For .Net Core it suffices to add "execute shell" build step with following script:

<pre class="lang-sh prettyprint-override"><code>#!bash -x

cd $my_project_dir
rm -rf TestResults # Remove old test results.
dotnet test -l trx
</code></pre>

After that add "Publish MSTest test result report" post-build action to make test results visible.

Default test reports path should be <code>**/*.trx</code> and will publish all produced <code>.trx</code> files.

I'm looking to run automated NUnit tests for a C# application, nightly and on each commit to svn.

Is this something that Jenkins-CI can do? 
Is there an online tutorial or how-to document which documents a similar setup that I can look at?

How do you run NUnit tests from Jenkins?

单元测试

服务器

我希望为C#应用程序运行自动化的NUnit测试，每晚在每次提交到svn时运行。这是Jenkins-CI可以做到的吗？是否有在线教程或how-to文档，其中记录了我可以查看的类似设置？

问如何从Jenkins运行NUnit测试？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从Jenkins运行NUnit测试？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从Jenkins运行NUnit测试？
EN