Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
grunt-stryker
Advanced tools
Professor X: For someone who hates mutants... you certainly keep some strange company.
William Stryker: Oh, they serve their purpose... as long as they can be controlled.
Stryker is a work in progress. We only support Jasmine tests in the browser for now. Please create and vote on stryker's issues to help us determine the priority on features.
This plugin requires Grunt ~0.4.5
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 using the following commands:
npm install stryker --save-dev
npm install grunt-stryker --save-dev
Once stryker and the plugin have been installed, the plugin may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-stryker');
In your project's Gruntfile, add a section named stryker
to the data object passed into grunt.initConfig()
and then add a task.
In this example we've called the task jasmine
due to the fact that we plan on using the task for running Jasmine tests, but feel free to use any name you want.
grunt.initConfig({
stryker: {
jasmine: {
files: {
libs: [/* List your library files here */],
src: [/* List your source files here */],
tests: [/* List your test files here */]
},
mutate: {
src: [/* List the files that you want to mutate here */]
}
},
},
});
Type: Object
An object with arrays of globbing expressions used for selecting all files needed to run the tests. These include: test files, library files, source files (the files selected with mutate
) and any other file you need to run your tests. The order of the files specified here will be the order used to load the file in the test runner (karma).
Type: Object
An object with arraysof globbing expressions used for selecting the files that should be mutated.
Type: string
A location to a config file. That file should export a function which accepts a "config" object. On that object you can configure all options as an alternative for the Gruntfile. If an option is configured in both the Gruntfile and in the config file, the Gruntfile wins. An example config:
module.exports = function(config){
config.set({
files: ['src/**/*.js', 'test/myFirstFile.spec.js', 'test/mySecondFile.spec.js'],
mutate: ['src/**/*.js'],
logLevel: 'debug'
});
}
Optional
Type: string
Default: "info"
Set the log4js loglevel. Possible values: fatal, error, warn, info, debug, trace, all and off. Note: We are still migrating to using log4js. Some messages are not configurable
In this example, we run mutation testing using every JavaScript file in the src
folder and every file in the test
folder except for test/IgnoredTestFile.js
.
We've called the task jasmine
here due to the fact that we plan on using the task for running Jasmine tests, but feel free to use any name you want.
Feel free to also choose the names of the arrays of files, we've used src
and tests
in this example.
grunt.initConfig({
stryker: {
jasmine: {
files: {
src: ['src/**/*.js'],
tests: ['test/**/*.js', '!test/IgnoredTestFile.js']
},
mutate: {
src: ['src/**/*.js']
}
},
},
});
In this example, we run grunt-stryker using a config file. We could overwrite the config file by manually configuring our grunt task as well.
grunt.initConfig({
stryker: {
jasmine: {
options: {
configFile: 'stryker.conf.js'
}
},
},
});
The content of the file stryker.conf.js
in this example is:
module.exports = function(config){
config.set({
files: ['src/**/*.js', 'test/myFirstFile.spec.js', 'test/mySecondFile.spec.js'],
mutate: ['src/**/*.js']
});
}
Note: It's not possible to exclude files in a config file using !
like: !myFile.js
. This is possible when you don't use a config file but define the options your Gruntfile
For the list of supported mutations, please take a look at the mutations supported by stryker
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.
FAQs
Grunt plugin for the mutation testing framework 'stryker'
The npm package grunt-stryker receives a total of 22 weekly downloads. As such, grunt-stryker popularity was classified as not popular.
We found that grunt-stryker demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.