![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
fru-grunt-coveralls
Advanced tools
Grunt task to load coverage results and submit them to Coveralls.io
Grunt task to load coverage results and submit them to Coveralls.io
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-coveralls --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-coveralls');
Grunt-coveralls takes one or more lcov files, and uploads them to coveralls.io.
Everything more specific than that is handled internally by node-coveralls, and the Coveralls service itself.
The only required option is a 'src' parameter, which accepts all the standard grunt src formats (plain path, glob, array of paths) and attempts to parse the matched lcov files and upload them.
This grunt task will pass as long as at least one file is matched, and all matched files are uploaded successfully.
grunt.initConfig({
coveralls: {
options: {
// LCOV coverage file relevant to every target
src: 'coverage-results/lcov.info',
// When true, grunt-coveralls will only print a warning rather than
// an error, to prevent CI builds from failing unnecessarily (e.g. if
// coveralls.io is down). Optional, defaults to false.
force: false
},
your_target: {
// Target-specific LCOV coverage file
src: 'coverage-results/extra-results-*.info'
},
},
});
This can then be run with grunt coveralls
or grunt coveralls:your_target
. For a practical example, look at this project, which uses itself to track its own coverage.
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. To ensure your code runs correctly, run npm test
.
(Nothing yet)
FAQs
Grunt task to load coverage results and submit them to Coveralls.io
We found that fru-grunt-coveralls demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.