beforeAll: not skipped within describe.skip

🐛 Bug Report

beforeAll functions are run even when defined inside of a describe.skip block.

To Reproduce

1. Define a describe.skip block.
2. Define a beforeAll inside the describe.skip block.
3. Do something within the beforeAll function to confirm that it does or does not get run (e.g. add a console.log statement, set some flag, etc.).

Expected behavior

The function registered by the beforeAll is never executed.

Link to repl or repo (highly encouraged)

https://repl.it/repls/UsableBurlyJavascript

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
  Binaries:
    Yarn: 1.2.1 - ~AppData\Roaming\npm\yarn.CMD
    npm: 6.0.0 - C:\Program Files\nodejs\npm.CMD

[mlopezluque]

This issue still remains when using the default jasmine2 runner.

I’ve made this gist with the same code as the issue’s repl using the latest version from Jest.

Output

Default jasmine2 runner

 jest

 FAIL  ./test.js
  ✕ should be skipped (8ms)
  Skipped suite
    ○ skipped 1 test
    Inner
      ○ skipped 1 test

  ● should be skipped

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      15 |
      16 | test("should be skipped", function() {
    > 17 |   expect(skipped).toBe(true);
         |                   ^
      18 | });
      19 |

      at Object.<anonymous> (test.js:17:19)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 2 skipped, 3 total
Snapshots:   0 total
Time:        1.017s
Ran all test suites.

Using jest-circus

Installing jest-circus and running the same gist with JEST_CIRCUS=1 produces the following output:

> jest

 PASS  ./test.js
  ✓ should be skipped (3ms)
  Skipped suite
    ○ skipped 1 test
    Inner
      ○ skipped 1 test

Test Suites: 1 passed, 1 total
Tests:       2 skipped, 1 passed, 3 total
Snapshots:   0 total
Time:        0.984s, estimated 1s
Ran all test suites.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.