Skip to content

fix(e2e): give the harness tests a timeout they can actually meet #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
CAMOBAP wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

fix(e2e): give the harness tests a timeout they can actually meet #120

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
241be83
fix(e2e): give the harness tests a timeout they can actually meet
CAMOBAP Oct 4, 2026
f7124f5
fix(e2e): set testTimeout where the harness actually reads it
CAMOBAP Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions __e2e__/rn-harness.config.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ const config = {

disableViewFlattening: true,
bridgeTimeout: 120000,
// Each case waits up to 10s for the WebView and then settles another 10s before
// screenshotting, so it needs more than the 5s default. This has to live here rather than
// as Jest's `testTimeout`: the harness reads `session.config.testTimeout` first and the
// schema always populates it, so a value in jest.harness.config.mjs is never consulted.
testTimeout: 60000,
forwardClientLogs: true,

runners: [
Expand Down
Loading