Jetpack/Testing: Difference between revisions

You can then run the debugger using that command.

You can run tests using the <code>cfx</code> command-line tool. There's [https://addons.mozilla.org/en-US/developers/docs/sdk/latest/dev-guide/addon-development/cfx-tool.html cfx documentation here], and command line help is available by typing:

   testall    - test whole environment

<code>cfx test</code> runs the tests implemented for a single SDK "package". A package is a collection of JavaScript modules, and is defined as such by the presence of a file called "package.json" in its root directory. Among other things, "package.json" includes an string called "tests" which describes where the package's test suites live. If this is not defined, the default is the "tests" or "test" directory under the package root.

An add-on is a package, and the SDK's APIs are currently collected into two packages called "addon-kit" and "api-utils" (you can see them under the top-level "packages" directory).

From the SDK root, navigate to "examples/reading-data" and explore the "tests" directory:

  Program terminated successfully.

An SDK package like "addon-kit" or "api-utils" is a package too, so the procedure is the same. Executing <code>cfx test</code> from the root of "addon-kit" will execute all the following test suites:

  Program terminated successfully.

<code>cfx testcfx</code> tests the <code>cfx</code> tool itself. <code>cfx</code> is written in Python, and <code>testcfx</code> uses Python's <code>unittest</code> framework.

It also looks for [http://docs.python.org/library/doctest.html DocTests] in the documentation files, and executes any that it finds. But there aren't any, at the moment.

<code>cfx testcfx</code> runs <code>cfx test</code> for all the add-ons which ship with the SDK under the examples/ directory.

<code>cfx testpkgs</code> finds all packages installed under the packages/ directory, and executes <code>cfx test</code> for each package it finds.

<code>cfx testall</code> tests everything: