<commit_before>js-test-tool
============

Run JavaScript test suites and collect coverage information.


Installation
------------

.. code:: bash

    cd js-test-tool
    python setup.py install


Getting Started
---------------

1. Create a file describing the test suite.

.. code:: bash

    js-test-tool init js_test.yml

This will create a YAML file (``js_test.yml``) that looks like:

.. code:: yaml

    ---
    # Name of the test suite, used to construct
    # the URL from which pages are served.
    #
    # For example, if the suite name is "test_suite",
    # then:
    #
    #   * /suite/test_suite
    #     serves the test suite runner page
    #   * /suite/test_suite/include/*
    #     serves dependencies (src, spec, lib, and fixtures)
    #
    # Test suite names must be URL-encodable and unique
    # among suite descriptions passed to js-test-tool
    test_suite_name: test_suite

    # Currently, the only supported test runner is Jasmine
    # See http://pivotal.github.io/jasmine/
    # for the Jasmine documentation.
    test_runner: jasmine

    # Path prepended to source files in the coverage report (optional)
    # For example, if the source path
    # is "src/source.js" (relative to this YAML file)
    # and the prepend path is "base/dir"
    # then the coverage report will show
    # "base/dir/src/source.js"
    prepend_path: base/path

    # Paths to library JavaScript files (optional)
    lib_paths:
        - path/to/lib

    # Paths to source JavaScript files<commit_msg>Update Jasmine link<commit_after>js-test-tool
============

Run JavaScript test suites and collect coverage information.


Installation
------------

.. code:: bash

    cd js-test-tool
    python setup.py install


Getting Started
---------------

1. Create a file describing the test suite.

.. code:: bash

    js-test-tool init js_test.yml

This will create a YAML file (``js_test.yml``) that looks like:

.. code:: yaml

    ---
    # Name of the test suite, used to construct
    # the URL from which pages are served.
    #
    # For example, if the suite name is "test_suite",
    # then:
    #
    #   * /suite/test_suite
    #     serves the test suite runner page
    #   * /suite/test_suite/include/*
    #     serves dependencies (src, spec, lib, and fixtures)
    #
    # Test suite names must be URL-encodable and unique
    # among suite descriptions passed to js-test-tool
    test_suite_name: test_suite

    # Currently, the only supported test runner is Jasmine
    # See https://jasmine.github.io/
    # for the Jasmine documentation.
    test_runner: jasmine

    # Path prepended to source files in the coverage report (optional)
    # For example, if the source path
    # is "src/source.js" (relative to this YAML file)
    # and the prepend path is "base/dir"
    # then the coverage report will show
    # "base/dir/src/source.js"
    prepend_path: base/path

    # Paths to library JavaScript files (optional)
    lib_paths:
        - path/to/lib

    # Paths to source JavaScript files
{'fraction_non_alphanumeric': 0.1059755694948828, 'fraction_numerical': 0.0006602839220864972, 'mean_word_length': 2.435374149659864, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1237934', 'n_tokens_mistral': 927, 'n_tokens_neox': 881, 'n_words': 333}