Open Source JavaScript Code Coverage Tools

Build powerful, scalable applications, with minimal overhead and full out-of-the-box functionality. Originally developed to handle Walmart’s Black Friday scale, hapi continues to be the proven choice for enterprise-grade backend needs. When you npm install @hapi/hapi, every single line of code you get has been verified. You never have to worry about some deep dependency being poorly maintained (or handed over to someone sketchy). hapi is the only leading node framework without any external code dependencies. None. hapi has been pushing the envelope on quality from day one. It was the first node framework to require and achieve 100% code coverage across every dependency – when everyone thought it was crazy. Every hapi feature is designed to make the platform easier and more intuitive to use. That means there’s no need to hack things together, experiment to see what *might* work, or try to figure out hidden internals. There is no “magic” – the code does what you expect.

Catberry is an isomorphic framework for building universal front-end apps using components, Flux architecture and progressive rendering. Catberry builds a bundle for running the application in a browser as a Single Page Application. Cat-Components – similar to web-components but organized as directories, can be rendered on the server and published/installed as NPM packages. The entire architecture of the framework is built using the Service Locator pattern, which helps to manage module dependencies and create plugins, and Flux, for the data layer. Search crawler receives a full page from the server. The whole state of the application is restored from URL. Server-side progressive rendering based on node.js streams and parallel rendering of components in a browser. The framework is well-tested (code coverage is about 90%) and it is already used in production.

A minimal skeleton for building testable React apps using Babel. The design goals are to use fewer tools (no yeoman, gulp, bower, etc...) Babel 6 with Webpack and Hot Loader. Fast testing with mocked-out DOM. Import CSS files as class names. Separate smart and dumb components. No specific implementation of Flux or data fetching patterns. A core philosophy of this skeleton app is to keep the tooling to a minimum. For this reason, you can find all the commands in the scripts section of package.json. This leverages React Hot Loader to automatically start a local dev server and refresh file changes on the fly without reloading the page. It also automatically includes source maps, allowing you to browse code and set breakpoints on the original ES6 code. Build minified app for production using the production shortcut.

A boilerplate application for building RESTful APIs Microservice in Node.js using express and mongoose in ES6 with code coverage and JsonWebToken Authentication. Helps you stay productive by following best practices. Follows Airbnb's Javascript style guide. JavaScript code linting is done using ESLint, a pluggable linter tool for identifying and reporting on patterns in JavaScript. Uses ESLint with eslint-config-Airbnb, which tries to follow the Airbnb JavaScript style guide. Supports code coverage of ES6 code using istanbul and mocha. Code coverage reports are saved in the coverage/directory post yarn test execution. Open coverage/lcov-report/index.html to view the coverage report. yarn test also displays code coverage summary on the console. Code coverage can also be enforced overall and per file as well, configured via .istanbul.yml.

Extends Cobertura to measure and report on code covered by unit tests in same package. Also adds improved reporting features, including measuring code coverage against a coverage policy.

ZK Unit extends JUnit to test your ZK project: ZUL pages, composers, event handlers, constraints and more. Use ZKUnit for test driven development, to achieve code coverage and integration with a continous build system.

This starter pack is designed to allow you to use a full set of the latest and coolest front-end technologies, all of which are configurable, feature-rich, code hot-loading based on webpack, css preprocessing using sass, unit testing, code coverage reporting, Code splitting and more. The main purpose of this project is to preserve as decisively as possible. The goal is not to follow this structure to complete your project, but to make front-end development more robust, simpler, and most importantly, happier. You can get all the features below! In the end, this project wouldn't be so robust without everyone's contributions. All relevant libraries are ready and waiting to be called at any time. The structure of this project uses fractal (irregular fractal: suitable for large projects), the grouping of methods is mainly by characteristics rather than file types. Note that this directory structure is only a guideline and does not have to be followed.