README.md

eslint-plugin-qunit

ESLint plugin containing rules useful for QUnit tests.

Available Rules

Below is the list of rules available in this plugin.

• assert-args
• literal-compare-order
• no-arrow-tests
• no-assert-equal
• no-async-in-loops
• no-async-test
• no-commented-tests
• no-compare-relation-boolean
• no-global-assertions
• no-global-expect
• no-global-module-test
• no-global-stop-start
• no-init
• no-jsdump
• no-negated-ok
• no-ok-equality
• no-only
• no-qunit-push
• no-qunit-stop
• no-reassign-log-callbacks
• no-reset
• no-setup-teardown
• no-test-expect-argument
• no-throws-string
• require-expect
• resolve-async

Available Configurations

You can extend from these configurations in order to simplify manual configuration of plugin rules in your project.

For more details on how to extend your configuration from one or both of these plugin configurations, please see the ESLint plugin configuration documentation.

recommended

This configuration includes rules which I recommend to avoid QUnit runtime errors or incorrect behavior, some of which can be difficult to debug. Some of these rules also encourage best practices that help QUnit work better for you.

You can use this configuration by extending from "plugin:qunit/recommended" in your configuration file.

Rules included in qunit/recommended configuration:

• assert-args
• literal-compare-order
• no-async-in-loops
• no-commented-tests
• no-ok-equality
• no-only
• no-reassign-log-callbacks
• no-reset
• require-expect (using "except-simple" configuration)
• resolve-async

two

This configuration includes rules which are useful for avoiding runtime errors or unexpected behavior in QUnit 2.0.

You can use this configuration by extending from "plugin:qunit/two" in your configuration file.

Rules included in qunit/two configuration:

• no-async-test
• no-global-assertions
• no-global-expect
• no-global-module-test
• no-global-stop-start
• no-init
• no-jsdump
• no-qunit-push
• no-qunit-stop
• no-reassign-log-callbacks
• no-reset
• no-setup-teardown
• no-test-expect-argument

Contributors

Thanks goes to these wonderful people (emoji key):

Kevin Partington 💻 📖 ⚠️ 🐛 💡 👀	Jordan Eldredge ⚠️ 💁	Mitch Lloyd 💻 📖 ⚠️	John Mainz ⚠️ 🐛

This project follows the all-contributors specification. Contributions of any kind welcome!

Semantic Versioning Policy

Like ESLint itself, this ESLint plugin follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy, based on the policy used by ESLint:

• Patch release (intended not to break your lint build)
  • A bug fix in a plugin rule that results in ESLint reporting fewer errors.
  • Improvements to documentation.
  • Non-user-facing changes such as refactoring code; adding, deleting, or modifying tests; and increasing test coverage.
  • Re-releasing after a failed release (i.e., after having published a release that doesn't work for anyone).
• Minor release (might break your lint build)
  • A bug fix in a rule that results in ESLint reporting more errors.
  • A new rule is created (without being added to plugin configuration).
  • A new option to an existing rule is created (without any default options changing).
  • A new plugin configuration is created.
  • An existing rule is deprecated.
• Major release (likely to break your lint build)
  • An existing plugin configuration is changed in any way, including but not limited to:
    • A new rule is added to the configuration.
    • A rule is removed from the configuration.
    • The options used in configuration for a rule are changed
  • An existing rule is removed.
  • A backward-incompatible change is made to the options of a rule.