Skip to content

test(e2e): check that a link opened through the SDK is stored as a human click - #13

Merged
onamfc merged 1 commit into
mainfrom
test/e2e-human-click
Oct 21, 2026
Merged

onamfc merged 1 commit into
mainfrom
test/e2e-human-click

Conversation

@onamfc

@onamfc onamfc commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

The server records a click when the SDK resolves a link the app opened. The end-to-end scenarios now check what it stored:

  • Link opened while the app runs and link that launches the app: exactly one click is stored for the link, and it is not classified as a bot.
  • Attributed install: the browser tap before the install is stored as human.

These are database checks, so they run when LF_E2E_DATABASE_URL is set. The SDK resolve's click is classified as human by @linkforty/core 1.35.3 and later; on an older server the Android checks fail (Android sends OkHttp's user agent, which earlier versions classified as a bot).

scenarios.mjs and harness.mjs are identical in the iOS and Android repos.

Results against a local server on @linkforty/core 1.35.3: 66 passed, 0 failed on both platforms. Against 1.35.0 the two Android open checks fail with "0 human, 1 bot".

…man click

The server records a click when the SDK resolves a link the app opened.
Check, for a link opened while the app runs and one that launches it, that
exactly one click is stored and that it is not classified as a bot; and
that the browser tap before an install is stored as human.
@onamfc
onamfc merged commit a2723d5 into main Oct 21, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants