chore(e2e): maintenance for automated tests after iOS 26.2 #3430

KrzysztofWojnar · 2025-11-27T17:58:42Z

Description

Closes https://github.com/software-mansion/react-native-screens-labs/issues/540

Broad changes after iOS 26.2 and some by-the-way fixes or improvements.
Not fixed tests:
iOS tests for example Test2809 should be aligned later with an output of PR #3303.
iOS tests for examples Test645 and Test649 are affected by issue #566

Changes

Detox e2e tests. Increased test isolation. Bar back button technical selector depends now on ios version.
Some android emulators my get a pop-up about using stylus which interrupts the test flow – it is disabled in the global config now.

Checklist

Included code example that can be used to test this change
Updated TS types
Updated documentation:
Ensured that CI passes

t0maboro

left some questions

Example/e2e/examplesTests/bottomTabs.e2e.ts

Example/e2e/examplesTests/events.e2e.ts

FabricExample/e2e/component-objects/back-button.ts

FabricExample/e2e/helpers/disableStylus.ts

FabricExample/e2e/component-objects/back-button.ts

kkafar

Hey! Thanks for the PR. I've left few questions & remarks. Please answer them (or let us know that the PR needs an assignee).

kkafar · 2025-12-05T10:36:13Z

Example/e2e/examplesTests/bottomTabs.e2e.ts

 describe('Bottom tabs and native stack', () => {
  beforeEach(async () => {
-    await device.reloadReactNative();
+    await device.launchApp({ newInstance: true });


I have a question here. Why do we relaunch application instead of reloading RN? This was done mostly to save CI time IIRC, so it is a subject to be changed, but I need reasoning here.

Yes, I discovered that the Example ("Paper") app behaves differently: the app may start ignoring touch events (the problem is most clearly visible on the SettingsPicker from apps\src\screens\Events.tsx:77, unluckly I lost the video with the proof). I don't know if the issue is in the react-native-screens or just in the test app. The logcat looked fine. I didn't have time to reproduce the exact conditions of the problem. But it [always] appeared only in these test suites (in different test cases) and only with automated executions (I failed with reproducing it manually, even accidentally).

Existing tests passed, when I added device.launchApp({ newInstance: true }); which increases their isolation.

kkafar · 2025-12-05T10:36:39Z

Example/e2e/examplesTests/events.e2e.ts

  beforeEach(async () => {
-    await device.reloadReactNative();
-    // await device.launchApp({ newInstance: true });
+    await device.launchApp({ newInstance: true });


Same here, and in every other place, where it has been done.

FabricExample/e2e/component-objects/back-button.ts

kkafar · 2025-12-05T10:40:13Z

FabricExample/e2e/component-objects/back-button.ts

I wonder about naming here. What are component-objects? Shouldn't be this kind of util directory with locators.js / actions.js?

yes, we can discuss that:
One of the top industry standards for e2e and ui automated tests is Page Object Model (a.k.a. Page Object Pattern) which separates behavior from a technical selectors and operations. This pattern is about having separate

test case files (the higher abstraction level, ideally even without touching automation library, like Selenium, Playwright, Detox etc),
"Page Object" files which define functions used be test cases (a middle abstraction layer that "maps" the elements and actions needed to execute the test with the automation library actions, so basically hiding all "technicall" elements(by.id(... and .tap() from test scenario)
and of course autamation library is the lowest abstraction layer in this pattern.

I tried also to re-invent wheel here as these Page Object files group actions and selectors depending on the page on which they are available (e.g. login/email and password inputs would be in the page-object/login.ts file) which is not usefull for us. I came up with an idea to shift focus on reusable componenst rather than pages...
Right now, there's only this header back button.
Should I move it and change the name (like e2e/component-objects/back-button.ts -> e2e/actions.ts)?

kkafar · 2025-12-05T10:44:49Z

FabricExample/e2e/component-objects/back-button.ts

+}
+async function getIOSBackButton() {
+  const iosVersion = semverCoerce(getIOSVersion().replace('iOS', ''))!;
+  if (semverSatisfies(iosVersion, '>=26.0')) {


Does this function work only on iOS 26+?

This function exists for iOS26+ but returns just the element(by.id('BackButton')) for other versions (line 34)

kkafar · 2025-12-05T10:48:42Z

FabricExample/e2e/issuesTests/Test2926.e2e.ts

    await element(by.id('home-button-open-second')).tap();

-    await element(by.id('BackButton')).tap();
+    await tapBarBackButton();


This is an iOS only test. We have nice & clean way to detect a back button & tap it & we replace it with the complicated logic in component-objects/back-button.ts? Why do we do this? My guess would be that this version does not work, but I need confirmation & explanation.

yes, selector element(by.id('BackButton')) resolves to two elements since iOS 26+ so taping on it with Detox causes an error.

KrzysztofWojnar · 2025-12-09T16:05:28Z

@kkafa

Hey! Thanks for the PR. I've left few questions & remarks. Please answer them (or let us know that the PR needs an assignee).

Adding an assignee could be helpful: I can answer in threads but this PR belongs directly to react-native-screens and I cannot change its code anymore. That means I need someone else to resolve conflicts (it seems we have some already) and merge the PR at the end. I can apply suggestions only by PRs from a fork (like I do in #3451).

The alternative is to close this PR and I could open a new one - entirely as a fork PR

kmichalikk · 2026-01-14T15:55:02Z

Cleaned up the PR a bit

removed linter fixes as they are a bit distracting (may be done in another PR)
refactored the helper classes
we need to decide whether we want component-object/ or just helpers/, and how to name those helpers (cc @kkafar)
reverted chore(CI): disable e2e workflows temporarily #2999 to see if the test are working

I keep the simulated scrolling instead of searching on iOS for now - this PR focuses only on making the CI complete successfully. This will be rewritten in a followup after #3532 and I will make the search work there.

FabricExample/e2e/issuesTests/Test432.e2e.ts

kmichalikk · 2026-01-15T11:45:05Z

Okay, so the CI passes, but there are lots of skipped tests (and I'm adding another one here, Test2809 which should be updated after #3303 anyways). Also there are .js files which are imported in TS and need .d.ts declarations - should we just rewrite them to TS? And there is still the question about file structure (see the comment above).

Co-authored-by: Krzysztof Ligarski <63918941+kligarski@users.noreply.github.com>

This reverts commit fee8faf.

KrzysztofWojnar requested review from kkafar, kligarski, kmichalikk and t0maboro and removed request for kkafar and t0maboro November 27, 2025 18:44

KrzysztofWojnar force-pushed the @KrzysztofWojnar/e2e-test-maintenance-ios-26.2 branch from a48c2f0 to e82c68e Compare November 28, 2025 10:09

t0maboro reviewed Nov 28, 2025

View reviewed changes

KrzysztofWojnar changed the title ~~WIP:chore(e2e): automated test maintenance for iOS 26.2~~ chore(e2e): automated test maintenance for iOS 26.2 Nov 28, 2025

KrzysztofWojnar changed the title ~~chore(e2e): automated test maintenance for iOS 26.2~~ chore(e2e): maintenance for automated tests after iOS 26.2 Nov 28, 2025

KrzysztofWojnar requested a review from t0maboro November 28, 2025 11:51

KrzysztofWojnar force-pushed the @KrzysztofWojnar/e2e-test-maintenance-ios-26.2 branch from d48d998 to 2401b65 Compare November 28, 2025 11:52

t0maboro approved these changes Nov 28, 2025

View reviewed changes

kligarski reviewed Dec 1, 2025

View reviewed changes

FabricExample/e2e/component-objects/back-button.ts Show resolved Hide resolved

FabricExample/e2e/helpers/disableStylus.ts Outdated Show resolved Hide resolved

FabricExample/e2e/component-objects/back-button.ts Outdated Show resolved Hide resolved

KrzysztofWojnar commented Dec 1, 2025

View reviewed changes

FabricExample/e2e/component-objects/back-button.ts Show resolved Hide resolved

kkafar reviewed Dec 5, 2025

View reviewed changes

kmichalikk self-assigned this Jan 14, 2026

kmichalikk force-pushed the @KrzysztofWojnar/e2e-test-maintenance-ios-26.2 branch from d3d7f11 to 6fb0bec Compare January 14, 2026 15:47

kmichalikk requested review from kkafar, kligarski and t0maboro and removed request for kmichalikk January 14, 2026 15:55

kmichalikk reviewed Jan 14, 2026

View reviewed changes

FabricExample/e2e/issuesTests/Test432.e2e.ts Show resolved Hide resolved

kmichalikk force-pushed the @KrzysztofWojnar/e2e-test-maintenance-ios-26.2 branch from 646238f to 97a0f5a Compare January 19, 2026 09:03

Bump react-native to 0.84-rc1

1d5be8a

Krzysztof Wojnar and others added 9 commits January 19, 2026 13:06

Fix e2e runner

7a9846e

Co-authored-by: Krzysztof Ligarski <63918941+kligarski@users.noreply.github.com>

Revert changes that do not belong to the issue

561a273

Revert "chore(CI): disable e2e workflows temporarily (#2999)"

46c2c86

This reverts commit fee8faf.

Refactor helpers

a29dcc5

Bump macos version in iOS workflows

2aa5d4c

Fix imports and tapBarBackButton usage on android

819ba60

Export command-line-helpers module for TS support

7155822

Fix imports, rollback Test432 change

9e77bf2

Temporarily disable Test2809

bffc313

kmichalikk force-pushed the @KrzysztofWojnar/e2e-test-maintenance-ios-26.2 branch from 97a0f5a to bffc313 Compare January 19, 2026 12:06

kmichalikk changed the base branch from main to @kmichalikk/rn-084-support January 19, 2026 12:08

Base automatically changed from @kmichalikk/rn-084-support to main January 19, 2026 15:29

Give more time for Test2963

5656a19

Uh oh!

chore(e2e): maintenance for automated tests after iOS 26.2 #3430

Are you sure you want to change the base?

chore(e2e): maintenance for automated tests after iOS 26.2 #3430

Conversation

KrzysztofWojnar commented Nov 27, 2025 • edited by kkafar Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Changes

Checklist

Uh oh!

t0maboro left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kkafar left a comment

Choose a reason for hiding this comment

Uh oh!

kkafar Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

KrzysztofWojnar Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kkafar Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kkafar Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

KrzysztofWojnar Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kkafar Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

KrzysztofWojnar Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

kkafar Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

KrzysztofWojnar Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

KrzysztofWojnar commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kmichalikk commented Jan 14, 2026

Uh oh!

Uh oh!

kmichalikk commented Jan 15, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

KrzysztofWojnar commented Nov 27, 2025 •

edited by kkafar

Loading

KrzysztofWojnar Dec 9, 2025 •

edited

Loading

KrzysztofWojnar Dec 9, 2025 •

edited

Loading

KrzysztofWojnar commented Dec 9, 2025 •

edited

Loading