bitHound Blog

Scoring test files in bitHound

All files should not be scored equally

Your test files and your project files have very different purposes, which means
they are coded differently. We're taking this into account in bitHound and are
now treating your test files differently so that we can provide you with
insightful and contextual recommendations.

While some factors such as the length of the file, and duplicate code are not
major indicators of problematic test files, complexity is. The more complex your
test files, the more likely you are to introduce false-negatives and/or
false-positives in your test results. We now take this into account when
displaying issues and scoring the health of your files.

Test files on bitHound

Along with these changes, we are introducing advancements to .bithoundrc. By
default we look for test, tests, spec and specs folders to identify your
test files. If you want to specify a different location, you can add a
.bithoundrc file to your project's root folder and specify your test folder location in the new tests section. For an example of what this looks like,
see our gist here.

bitHound identifies risks and priorities in your Node.js projects.