Using the Chutzpah.json Settings File

The Chutzpah settings file is an .json file that you can place anywhere in your testing directories to inform Chutzpah of test specific settings. The Chuzpah settings file is completely optional and if the file or any of its properties are omitted Chutzpah will use the default values.

When Chutzpah is run on a file (lets say test.js) it scans the current directory for a file named chutzpah.json. If it does not find one it will recursively traverse up the directory chain looking for one. This behavior provides a lot of flexibility since you can provide multiple chutzpah.json files in your tree and each one will work over its sub-folder. This lets you have different settings for different groups of tests.

Important: The deserializer Chutzpah uses is is restrictive about what you put in your chutzpah.json file. To make sure it parses correctly make sure you surround all properties in quotes and do not put comments in the file.

The settings file is a text file with json content of the following format:

{
    "Framework": "qunit|jasmine|mocha",

    "FrameworkVersion": "",
    
    "TestFileTimeout": "<Timeout in milliseconds>",
    
    "TestHarnessLocationMode": "TestFileAdjacent|SettingsFileAdjacent|Custom",
    
    "TestHarnessDirectory": "<Path to a folder>",

    "TestHarnessReferenceMode": "Normal|AMD",
    
    "RootReferencePathMode":"DriveRoot|SettingsFileDirectory",
    
    "CodeCoverageIncludes": [],
    
    "CodeCoverageExcludes": [],

    "EnableCodeCoverage": "true|false",

    "References": [],

    "Tests": [],

    "CoffeeScriptBareMode": "true|false",

    "CustomTestHarnessPath": "<Path to custom test harness file>",

    "Compile": <A compile configuration object>,

    "TestPattern": "<Regex test name pattern>",

    "AMDBasePath": "<Path to same location that your Require.js config baseurl points to>",

    "TypeScriptCodeGenTarget" : "ES3|ES5",

    "TypeScriptModuleKind" : "CommonJS|AMD",

}

The chutzpah.json file supports the following properties

Framework – Determines what testing framework to use. This will override the other detection methods. This is helpful if Chutzpah is having trouble figuring out what your intended framework is. If left out Chutzpah will automatically try to detect the framework.

FrameworkVersion - Tells Chutzpah if it should use a different version of on of the test frameworks than the default one. Currently, the only framework this works for is Jasmine. As of the 3.1.0 release Chutzpah default to Jasmine 2.0 but if you want to use the 1.0 line for Jasmine still pass "1" for FrameworkVersion.

References - Using the references setting

Tests - Using the tests setting

Compile - Using the compile setting


TestFileTimeout - The time to wait for tests in a file to finish in milliseconds

TestHarnessLocationMode – Determines where to place the generated html test harness files. The default mode is TestFileAdjacent which means the harness is placed in the same directory as the test file. SettingsFileAdjacent means it is placed in the same directory as the chutzpah.json file. Custom mode lets you specify a custom path to the directory.

TestHarnessDirectory – When TestHarnessLocationMode is set to Custom this is either the relative or absolute path to the directory where to place the test harness.

RootReferencePathMode – This property determines what directory a rooted reference path refers to. In a test file Chutzpah parses the <reference path="" /> tags to determine your test dependencies. By default (the DriveRoot setting) if you write <reference path="\a.js" /> Chutzpah will look for a.js under C:\ (assuming you are running your test in the C drive). However, if you set this property to SettingsFileDirectory Chutpah will now look for a.js relative to the location of the chutzpah.json file. This is useful if you have a large project and want to minimize the number of long reference paths.

CodeCoverageIncludes - The collection code coverage file patterns to include in coverage. These are in glob format. If you specify none all files are included.

CodeCoverageExcludes - The collection code coverage file patterns to exclude in coverage. These are in glob format. If you specify none no files are excluded.

CustomTestHarnessPath - The CustomTestHarnessPath setting allows you to override the default template Chutzpah uses for the HTML test harness. This is an advanced feature which should only be used as a last resort. Read how to use it in Customizable HTML harness generation.

CoffeeScriptBareMode - The CoffeeScriptBareMode indicates if you want CoffeeScript compilation to output scripts in bare mode or not. In bare mode CoffeeScript won’t wrap the generated JavaScript in a function to protect the scope. The default value is true.

AMDBasePath - Lets you configure Chutzpah to work in with RequireJS when you are setting a baseurl in your Require.js config. This should point to the same location. See this example.

TestPattern - Using the TestPattern setting

Examples:

This file tells Chutzpah to use QUnit and to place the test harness next to the chutzpah.json file:
{
    "Framework": "qunit",
    "TestHarnessLocationMode": "SettingsFileAdjacent"
}

This file tells Chutzpah to convert TypeScript to ES5 code and to place the test harness in a custom directory:
{
    "TypeScriptCodeGenTarget" : "ES5",
    "TestHarnessLocationMode": "Custom",
    "TestHarnessDirectory": "../Some/Folder"
}

When run with Code Coverage this file tells Chutzpah to exclude files named jquery.js and include files that have a suffix of query.js or are named dogs.js:
{
    "CodeCoverageExcludes": ["*\\jquery.js"],
    "CodeCoverageIncludes": ["*query.js", "*\\dog.js"]
} 


Last edited May 13 at 3:33 PM by mmanela, version 29