grunt-mstest
Advanced tools
Comparing version 0.1.2 to 0.1.3
@@ -87,2 +87,5 @@ /* | ||
// plugin's task(s), then test the result. | ||
process.env.VS100COMNTOOLS = "Durp"; | ||
grunt.registerTask('test', ['clean','msbuild', 'mstest', 'nodeunit']); | ||
@@ -89,0 +92,0 @@ |
{ | ||
"name": "grunt-mstest", | ||
"description": "The best mstest Grunt plugin ever.", | ||
"version": "0.1.2", | ||
"version": "0.1.3", | ||
"homepage": "https://github.com/mrjackdavis/grunt-mstest", | ||
@@ -32,5 +32,6 @@ "author": { | ||
"grunt-contrib-clean": "~0.4.0", | ||
"grunt-contrib-nodeunit": "~0.2.0", | ||
"grunt-contrib-nodeunit": "~0.3.3", | ||
"grunt": "~0.4.2", | ||
"grunt-msbuild": "~0.1.9" | ||
"grunt-msbuild": "~0.1.9", | ||
"nodeunit": "~0.8.6" | ||
}, | ||
@@ -37,0 +38,0 @@ "peerDependencies": { |
@@ -22,65 +22,16 @@ # grunt-mstest | ||
### Overview | ||
In your project's Gruntfile, add a section named `mstest` to the data object passed into `grunt.initConfig()`. | ||
### Sorry, | ||
I haven't gotten around to writing the documentation for this yet. | ||
```js | ||
grunt.initConfig({ | ||
mstest: { | ||
options: { | ||
// Task-specific options go here. | ||
}, | ||
your_target: { | ||
// Target-specific file lists and/or options go here. | ||
}, | ||
}, | ||
}); | ||
``` | ||
Nevertheless here's an example: | ||
### Options | ||
#### options.separator | ||
Type: `String` | ||
Default value: `', '` | ||
A string value that is used to do something with whatever. | ||
#### options.punctuation | ||
Type: `String` | ||
Default value: `'.'` | ||
A string value that is used to do something else with whatever else. | ||
### Usage Examples | ||
#### Default Options | ||
In this example, the default options are used to do something with whatever. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result would be `Testing, 1 2 3.` | ||
```js | ||
grunt.initConfig({ | ||
mstest: { | ||
options: {}, | ||
files: { | ||
'dest/default_options': ['src/testing', 'src/123'], | ||
}, | ||
```javascript | ||
mstest: { | ||
myTest: { | ||
src: ['tmp/*.dll'] // Points to test dll | ||
}, | ||
}); | ||
} | ||
``` | ||
#### Custom Options | ||
In this example, custom options are used to do something else with whatever else. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result in this case would be `Testing: 1 2 3 !!!` | ||
```js | ||
grunt.initConfig({ | ||
mstest: { | ||
options: { | ||
separator: ': ', | ||
punctuation: ' !!!', | ||
}, | ||
files: { | ||
'dest/default_options': ['src/testing', 'src/123'], | ||
}, | ||
}, | ||
}); | ||
``` | ||
## Contributing | ||
@@ -90,3 +41,4 @@ 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](http://gruntjs.com/). | ||
## Release History | ||
- 0.1.3 Change priority of vstools to newest first | ||
- 0.1.2 Fix issue where vstools 10 or 12 was not detected | ||
- 0.1.0 Initial release |
@@ -56,4 +56,4 @@ /* | ||
function getExePath() { | ||
//Possible env variables for visual studio tools, in order of priority | ||
var vsToolsArr = [process.env.VS120COMNTOOLS,process.env.VS110COMNTOOLS,process.env.VS100COMNTOOLS] | ||
//Possible env variables for visual studio tools, in reverse order of priority | ||
var vsToolsArr = [process.env.VS100COMNTOOLS,process.env.VS110COMNTOOLS,process.env.VS120COMNTOOLS] | ||
@@ -60,0 +60,0 @@ //Get highest priority VS tools |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
181
51970
6
43
5