lichtenberg
A tracing program for your JavaScript apps.
Last updated 5 years ago by baconscript .
ISC · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install lichtenberg -g
SYNC missed versions from official npm registry.

Lichtenberg

Lichtenberg figure, made by high-voltage electrical discharge through a block of acrylic

A JavaScript code coverage and debugging library. Still in alpha.

NPM version NPM downloads License

What is it?

Lichtenberg reads your code and annotates it with trace statements. Then, when you view your tests in a browser, it watches for those trace statements and keeps track of how many were run. From this, it creates a coverage report telling you how much of your code was actually run during the test. Strive for 100%!

Lichtenberg aims to be as independent as possible of whatever testing framework you choose. It's been proven to work with Mocha, but should also work with QUnit, Jasmine, etc.

Installing

$ npm install -g lichtenberg

Trying it out

You can try Lichtenberg with the sample test folder included in this repository. Requires Grunt.

$ git clone https://github.com/baconscript/lichtenberg.git
$ cd lichtenberg
$ npm install && grunt
$ cd test
$ lichtenberg

Try adding more tests in test.html and watching the coverage go up! The library being tested is format.

Setup

To run Lichtenberg coverage on your project, first create a lichtenberg.json file in your project root.

{
  "entry": "test.html",
  "include": ["assets"],
  "exclude": ["bower_components"],
  "serveAs": "/apps/myApp"
}
  • entry: HTML page that runs your tests. Lichtenberg will inject a couple of script tags and a div into it to generate the code coverage.
  • include: Regular expression indicating which files to instrument for coverage.
  • exclude: Regular expression indicating which files to ignore when instrumenting. Good candidates for this would be any external libraries you're using.
  • serveAs: Path to your entry point on the server. This is helpful if you have absolute paths in your code and need to preserve them. For instance, if your test page is served at /apps/myApp/test.html, setting serveAs to be /apps/myApp will serve all the files in the project from that path.

Add __Lichtenberg.done() to your code

In your test suite, add the following code in a place where it will run after all tests should have completed.

if(window.__Lichtenberg) {
  __Lichtenberg.done();
}

Or, if you want something shorter: window.__Lichtenberg && __Lichtenberg.done()

In Mocha's BDD style, this may be achieved by wrapping all your tests in a describe() and adding the code to an after() function.

When done() is called, Lichtenberg runs through all the lines of code that it is aware of, computes coverage on each file, and displays the results in your browser.

Running

From the same directory as your lichtenberg.json file, just type lichtenberg to start the server. Visit http://localhost:9796 in your browser to view the results. Report generation is coming soon.

Sample tests using Mocha

Current Tags

  • 0.0.4                                ...           latest (5 years ago)

2 Versions

  • 0.0.4                                ...           5 years ago
  • 0.1.0                                ...           5 years ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 2
Dependencies (9)
Dev Dependencies (4)
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |