Shulou(Shulou.com)05/31 Report--

This article mainly explains "what testing tools are there in javascript", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn "what testing tools are there in javascript"?

Overview

The four tools work in the same basic way. They all have a set of rules for users to analyze and report errors in js files. They can all be installed through npm. They can all be used from the command line, as Grunt plug-ins, or integrated into editors. All four of them support configuration using annotations.

But the similarity is over. Each tool has its own advantages and disadvantages-the advantages are obtained by comparison.

JSLint

JSLint is one of the oldest tools. Douglas Crockford developed the tool in 2002 and, based on its experience, enforces the use of the essence of the js language If you agree with these essentials, JSLint can be a good tool.

The disadvantage of JSLint is that it cannot be configured and extended. You can't ban the need for features at all, and many of them lack documentation. Official documentation is very unfriendly, such as the lack of information on how to integrate it into editors.

Advantages

Parameter configuration is complete, and you can directly use the

Shortcoming

There is no configuration file in JSLint. If you want to change the parameter settings, there is a problem.

Limited configuration options, many rules cannot be banned

Cannot add personalization rules

No documentation rules

It is difficult to figure out which rule caused the error

JSHint

As a configurable version of JSLint, JSHint was developed. You can configure each rule and put it in a configuration file so that it can be easily used in large projects. JSHint has good documentation for each rule, so you can know exactly what each rule does. It is also easy to integrate it into the editor.

One small drawback of JSHint is its loose default configuration. That is, you have to start it before you can make it available. Compared with ESLint, it is more difficult for JSHint to determine which rule user turns on or off error messages.

Advantages

Mostly the parameters can be configured.

Support for configuration files, easy to use in large projects

Support for required class libraries, such as jQuery, QUnit, NodeJS, Mocha, etc.

Support for basic ES6

Shortcoming

It is difficult to know which rule makes an error

There are two types of options: mandatory options and loose options. Makes the configuration a little confusing.

Custom rules are not supported

JSCS

JSCS is different from others because if you don't give it a configuration file or tell it a configuration item, JSCS

Won't do anything. You can save their site configuration items now, so this is not a big problem, and there are many configuration items, such as jQuery code style configuration items, Google configuration items.

It has more than 90 different rules, and custom rules can be created through plug-ins. When integrating with other tools requires a specific format, JSCS also supports custom reports to make it very easy.

JSCS is a code style checker. This means that it only matches the code format problem, not the potential bugs, errors. Therefore, it is less flexible than other tools, but if you only force checking the code style, JSCS is also a good tool.

Advantages

Support for custom reports for easier integration with other tools

If you follow an available code style, configure items and prepared configuration files to make it easy to start

There is a tag in the report that contains the name of the rule, so it is easy to indicate which rule caused the error

Expand through custom plug-ins

Shortcoming

Just check for code style issues. JSCS does not check for potential bugs, such as inapplicable variables, accidental global variables, and so on

The slowest of the four tools, but not a problem in use

ESLint

ESLint is a tool that comes out of *. It is designed to be easy to expand, has a large number of custom rules, and is easy to install through plug-ins. It gives the exact output and includes the name of the rule so that you can know which rule caused the error.

The ESLint documentation is somewhat confusing. Rules are easy to find and are divided into logical groups, but configuration guidelines are easy to get confused in some places. However, it can provide links to edit integrations, plug-ins, and samples in one place.

Advantages

Flexibility: any rule can be opened and closed, and some rules have some additional configuration

It is easy to expand and plug-ins are available when needed

Easy to understand output

Contains rules that are not available in other inspectors, making ESLint more useful in error checking

Support for ES6, the only tool that supports JSX

Support for custom reports

Shortcoming

Need some configuration

Slow, but not a major problem

At this point, I believe you have a deeper understanding of "what testing tools are there in javascript?" you might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.