# ember/no-test-module-for

💼 This rule is enabled in the ✅ `recommended` [config](https://github.com/ember-cli/eslint-plugin-ember#-configurations).

<!-- end auto-generated rule header -->

Use `module` instead of `moduleFor`.

`moduleForComponent`, `moduleFor`, `moduleForAcceptance`, etc have been deprecated and there are codemods to help migrate.

## Examples

Examples of **incorrect** code for this rule:

```js
import { moduleFor } from 'ember-qunit';

moduleFor('Test Name');
```

Examples of **correct** code for this rule:

```js
import { module } from 'qunit';

module('Test Name', function (hooks) {
  // ...
});
```

## Migration

A short guide for how each of the legacy APIs converts to the new APIs:

- `moduleFor`, `moduleForModel`

  ```js
  import { module, test } from 'qunit';
  import { setupTest } from 'ember-qunit';

  module('...', function (hooks) {
    setupTest(hooks);
  });
  ```

- `moduleForComponent`

  ```js
  import { module, test } from 'qunit';
  import { setupRenderingTest } from 'ember-qunit';

  module('...', function (hooks) {
    setupRenderingTest(hooks);
  });
  ```

- `moduleForAcceptance`

  ```js
  import { module, test } from 'qunit';
  import { setupApplicationTest } from 'ember-qunit';

  module('...', function (hooks) {
    setupApplicationTest(hooks);
  });
  ```

## References

- [moduleFor\* deprecation notice from ember-qunit 4.5.0](https://github.com/emberjs/ember-qunit/blob/master/CHANGELOG.md#rocket-enhancement-1)

- Codemod for automated upgrade of tests: [ember-qunit-codemod](https://github.com/ember-codemods/ember-qunit-codemod)