# jest/padding-around-after-all-blocks

> Require a blank line before each `afterAll` call

An `afterAll` hook right under another statement is easy to miss when you're looking for a file's cleanup code. A blank line above it makes it stand out.

The rule only checks the line above the call, not the line below. Comments directly above the call count as part of it, so the blank line goes above them. An `afterAll` that comes first in a file or in a `describe` callback doesn't need a blank line.

`--fix` inserts the blank line.

{/* Generated by src/codegen/lint-rule-docs.ts. Do not edit this section. */}

## Configure

Off by default. To turn it on:

```toml bunfig.toml
[lint.rules]
"jest/padding-around-after-all-blocks" = "error" # or "warn"
```

{/* End of the generated section. */}

## Examples

Reported:

{/* bad */}
```js
import { afterAll, describe } from "@jest/globals";

describe("database", () => {
  const db = connect();
  afterAll(() => db.close());
});
```

Two `afterAll` calls in a row need a blank line between them too:

{/* bad {"count": 2} */}
```js
import { afterAll } from "@jest/globals";

const server = startServer();
afterAll(() => server.stop());
afterAll(() => removeTempFiles());
```

Not reported:

{/* good */}
```js
import { afterAll, describe } from "@jest/globals";

describe("database", () => {
  const db = connect();

  // Close the connection so the process can exit.
  afterAll(() => db.close());
});
```