Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

afterEach hooks run outer suite first, unlike Jest

Open Beginner friendly
  • Is something wrong?
#296 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react-native, typescript
Domain
mobile, testing

Research direction

Start with collectInheritedHooks in packages/runtime/src/runner/hooks.ts, then read the existing tests for beforeEach and afterEach hook order. Reproduce the reported order with nested suites and verify the hooks run innermost first for afterEach while beforeEach keeps its current order. Done when the test confirms the reported behavior is fixed.

Written by the indexing model from the issue text.

Description

Describe the bug

collectInheritedHooks in packages/runtime/src/runner/hooks.ts collects hooks from the root suite down and runs them in that order for both beforeEach and afterEach.

Jest and Vitest run afterEach the other way round, innermost suite first. So an afterEach in setupFilesAfterEnv runs before a test file’s own afterEach. Anything that checks cleanup at the top level then sees resources the test hasn’t closed yet. Reversing the list for afterEach fixes it.

We have a library that runs in both Node.JS and React Native through different native bindings and we reuse the same test suite between them.

System Info
System:
  OS: macOS 15.6
  CPU: (14) arm64 Apple M4 Pro
  Memory: 141.98 MB / 48.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 24.16.0
    path: /Users/user/.nvm/versions/node/v24.16.0/bin/node
  Yarn:
    version: 1.22.22
    path: /Users/user/.nvm/versions/node/v24.16.0/bin/yarn
  npm:
    version: 11.13.0
    path: /Users/user/.nvm/versions/node/v24.16.0/bin/npm
  Watchman:
    version: 2025.10.20.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 25.2
      - iOS 26.2
      - macOS 26.2
      - tvOS 26.2
      - visionOS 26.2
      - watchOS 26.2
  Android SDK:
    API Levels:
      - "34"
      - "35"
      - "36"
      - "37"
    Build Tools:
      - 34.0.0
      - 35.0.0
      - 36.0.0
      - 36.1.0
      - 37.0.0
    System Images:
      - android-24 | Google APIs ARM 64 v8a
      - android-29 | Google APIs ARM 64 v8a
      - android-35 | ARM 64 v8a
      - android-35 | Google APIs ARM 64 v8a
      - android-36.1 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2025.1 AI-251.27812.49.2514.14217341
  Xcode:
    version: 26.2/17C52
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.17
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.2.0
    wanted: latest
  react:
    installed: 19.3.0
    wanted: 19.3.0
  react-native:
    installed: 0.88.0
    wanted: 0.88.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: true
  newArchEnabled: true
React Native Harness Version

1.6.0

Reproduction

https://github.com/TimoGlastra/harness-aftereach-repro/commit/6bae61176e88fe33a14953ad755b35dddbd37d6b

Steps to reproduce
  1. npm install
  2. npx expo run:ios --no-bundler to build and install the app. If you don't have an iPhone 17 Pro simulator on iOS 26.2, change the simulator in rn-harness.config.mjs first.
  3. npm run test:ios

The second test in afterEach.harness.ts fails:

● inner › afterEach hooks of the first test ran inner first
  expected 'outer afterEach > inner afterEach' to be 'inner afterEach > outer afterEach'

The outer suite's afterEach runs before the inner suite's. Jest and Vitest run afterEach hooks from the innermost suite outwards. It happens on every platform: the order comes from collectInheritedHooks in packages/runtime/src/runner/hooks.ts, which returns the hooks root first for afterEach as well as beforeEach. Reversing the list for afterEach makes the test pass.

Dominant language
TypeScript
Stars
335
Forks
23
Avg merge
1d 8h
Merged PRs (30d)
53

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstackincubator/react-native-harness

All issues in callstackincubator/react-native-harness

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.