-
Notifications
You must be signed in to change notification settings - Fork 0
XUnit Task
The XUnitTask is designed to run tests written with the xunit test framework.
There are only a few pieces of information needed for the XUnitTask to operate correctly. Most notably are the path to the xunit-console executable, and a list of assemblies for xunit to run tests against.
For example
desc "XUnit Test Runner Example"
xunit do |xunit|
xunit.command = "XUnit/xunit.console.exe"
xunit.assembly = "assemblies/TestSolution.XUnitTests.dll"
end
You must provide the location of the xunit console executable either through the constructor or via the .command setting.
You must provide a single assembly or array of assemblies for xunit to run. These should be assemblies that contain your [Fact]s. The xUnit runner does not allow more than one assembly to be specified, so command will be started for each individual assembly.
You can specify additional parameters for the xunit executable here. If the options require a “/”, “-”, or any other special character, be sure to include that in the option.
Like the assemblies setting, options is an array that can be wholesale replaced or appended to.
xunit.options '/someoption', '/anotheroption'You can specify the folder to write an html report of the tests to.
Prevent Rake from aborting the build when an xunit test fails. This is useful in continuous integration scenarios, such as running with TeamCity. For now, you have to set this to some value, like
xunit.skip_test_fail = trueThis task supports configuration via an external YAML file. For more information, see the yamlconfig page.
This task supports additional command line options, including a .parameters collection for passing in options that are not directly supported. For more information, see the commandline task options documentation.
- Build-Server Integration
- Command Line Task Options
- Configuration
- Custom Tasks
- Logging Options
- Sample Usages
- Task Arguments and Rakefile Parameters
- YAML Configuration
- ASP.NET Compiler - ASP.Net website compiler
- Assembly Info Generator - generate assembly info dynamically
- CSC - C# compiler
- Exec - Execute arbitrary cmd
- Fluent Migrator - Run FluentMigrator on migration library
- ILMerge - Merge dll/exe-s together
- MSBuild and XBuild - Compile a .sln-file or a MsBuild xml-file
- MSpec - Test using MSpec (machine.specifications)
- MSTest - Test using Microsoft Test Framework
- NAnt - Run a NAnt script
- NChurn - Calculate per-file churn
- NCover Console - Run NCover for tests/library
- NCover Reports - Generate a report from a coverage run
- NDepend - Run NDepend to check static code metrics
- NuGet Install - Install NuGet packages
- NuGet Pack - Create NuGet packages
- NuGet Push - Push NuGet packages to official MS repo
- NuGet Publish - Publish NuGet packages
- NUnit - Test using NUnit
- NuSpec - Generate a NuSpec file
- Output - File copying and template expansion
- PLink - SSH into a remote computer and run a command
- SQLCmd - Run a SQL command as a part of your build process
- UnZip - Unzip a directory
- XBuild - Run XBuild (will be merged into MsBuild)
- XUnit - Test using XUnit
- Zip - Zip a directory or files
- Edit the Wiki Locally - How to edit the wiki without using Github's interface
- How to Build Albacore
- How to Contribute