Grunt plugin to run Machine.Specfication tests
This plugin requires Grunt ~0.4.2
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-dotnet-mspec --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-dotnet-mspec');
In your project's Gruntfile, add a section named mspec
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
mspec: {
options: {
// Task-specific options go here.
},
your_target: {
// Target-specific file lists and/or options go here.
},
},
});
Type: String
Default value: ``
A string value pointing to the mspec tools folder (this folder should contain the mspec-clr4.exe etc.).
Type: String
Default value: reports/mspec
A string value pointing to the folder where the reports should be generated.
Type: Boolean
Default value: true
A boolean value indicating if time related info should be shown in the html report.
Type: Boolean
Default value: false
A boolean value indicating if progress should be suppressed (only print fatal errors, failures and summary).
Type: Boolean
Default value: false
A boolean value indicating if progress should be shown as dotted output.
Type: String
Default value: anycpu
Possible values: anycpu|x86
A string value indicating what platform to use for running the tests
The toolsPath in this example points to the mspec nuget package tools folder. The report will be stored in the reports folder relative to your grunt file. The specs target will execute all dll's ending with Spec.dll
located in all bin/Debug
folders within the test/src
folder.
grunt.initConfig({
mspec: {
options: {
toolsPath: 'test/src/packages/Machine.Specifications.0.6.2/tools',
output: 'reports/mspec'
},
specs: {
src: ['test/src/**/bin/Debug/*Specs.dll']
}
},
});
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
(Nothing yet)