Repository navigation
End to end tests - #2209
Merged
Merged
End to end tests#2209
Conversation
ludomikula
force-pushed
the
e2e-playwright-tests
branch
from
November 22, 2026 14:04
c6391f9 to
186a351
Compare
Add an e2e/ package that runs Playwright from the official runner image against a fresh all-in-one Lowcoder container and a PostgreSQL sidecar, started and removed by e2e/scripts/run-in-docker.sh. Tests: sign-up, sign-in and sign-out, wrong password, drag from the insert panel, editing a property, published view versus draft, public and private apps for a visitor, trash and restore, invited member permissions, and PostgreSQL queries in the editor and in a published app. Every browser context blocks all origins except the app under test, so no request reaches lowcoder.cloud or HubSpot; there is no way to switch this off. Claude-Session: https://claude.ai/code/session_015KPtHKPW6LJoxzf4tn8Rtm
Add four attributes the tests need, without changing behaviour or layout: data-editor-ready on the editor once its save baseline exists, data-testid="insert-comp-<type>" on insert-panel tiles, role="tab" and aria-selected on the right-panel tabs, and data-comp-name on canvas items. The tests now wait for the ready marker instead of a fixed wait, find tiles by test id and tabs by role. scripts/build-e2e-image.sh builds the image the tests default to (the 3.0.0 all-in-one image with this client). A quarantined test records that a component dropped right after the editor is ready gets width 0. Claude-Session: https://claude.ai/code/session_015KPtHKPW6LJoxzf4tn8Rtm
….0.0 Block WebSocket connections to other hosts in every browser context and block service workers in extra sessions; refuse a second run on one checkout; assert the permission message a member without a grant sees; name the literals of the editor tests; drop an unused helper. The test image is now built from the client of the 3.0.0 release plus the testability hooks in e2e/client-hooks.patch instead of the current checkout. Claude-Session: https://claude.ai/code/session_015KPtHKPW6LJoxzf4tn8Rtm
… end-to-end tests Claude-Session: https://claude.ai/code/session_015KPtHKPW6LJoxzf4tn8Rtm
…client's hocuspocus URL The app container gets the network alias lowcoder-e2e-app, and the tests reach it under that name. The test image is built with REACT_APP_HOCUSPOCUS_URL pointing at the app's own /hocuspocus proxy, so the chat components connect through the app origin and the network guard stays unchanged. The shared names live in e2e/scripts/app-host.sh. Claude-Session: https://claude.ai/code/session_015KPtHKPW6LJoxzf4tn8Rtm
…-to-end suite Implements the component test plans on top of the Docker harness: - foundation: recorded component DSL, builders (components, queries, events, transformers, data responders, modules), page objects (table, extensions panel, property panel actions), createModule, 25-row products fixture, media fixtures, @insert-all run selection and a D-3 threshold reporter - scenarios: S1 insert-every-tile (nightly), S2-S14 inputs, choices, dates, sliders, buttons, displays, containers, overlays, forms, media, lists, timer, S15-S20 npm components, plugins, chat and iframe - L1-L3 temporary state, local storage and query triggers, D1/D2 data feeding components and the table, M1-M3 modules - e2e/README.md, AGENTS.md and CLAUDE.md describe the harness and the rules for writing tests The default run holds 242 tests; S1 (112) and the quarantined tests are opt-in. Known defects are annotated, not hidden (D-3, CD-5, CD-7). Claude-Session: https://claude.ai/code/session_015KPtHKPW6LJoxzf4tn8Rtm
…ss-organization access Adds specs for cross-organization access, role and admin/viewer rights, credentials, mass assignment, group grants, membership changes, public leakage, the collab room, transport, enterprise mode and outbound requests, with supporting actors, assertions, a super-admin actor, an HTTP echo sidecar and an optional enterprise stack. Tests that assert desired behaviour the 3.0.0 server does not yet have are quarantined behind opt-in tags and flags; the README lists the findings and run selection. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
…o-end suite Lifecycle tests get ids LC-<area><nn>, the @lifecycle tag and detail functions that share the quarantine maps with the security ids; the detail factory takes an injected lookup so the listed-id branches are unit tested before any lifecycle test is mapped. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
… lifecycle suite Sixteen lifecycle tests: a registered or malformed address, the password rules and the confirmation check of the sign-up form, the invitation link, the workspace sign-up page, the unknown address, choosing among two workspaces, UI sign-out ending the server session, the cookie lifetime and the redirects of signed-in and anonymous visitors. Two are quarantined: the server enforces no password rule (D-48) and a sign-up on a workspace's sign-up page joins that workspace (D-30). Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
Fifteen lifecycle tests: display name on the profile page and in the My Profile modal, an empty name, avatar upload, an SVG and an oversized avatar, avatar delete, UI language, status flags, and the password change in the modal and through the API. Three are quarantined: the server accepts a password replaced without the old one (D-49), a new password the client rule refuses (D-48) and an avatar above the size limit (D-50). Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
Eight lifecycle tests on the API key card of the profile page: a key created in the UI authenticates, the token is shown once and listed masked, a key deleted in the UI stops working, a plain member gets no card, a name is required, a key follows the user's current workspace, and two keys of one second never share a token. Two are quarantined because the 3.0.0 image keeps the last key listed (D-45) and gives such keys the same token (D-51); both are fixed on this branch. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
… suite Nine lifecycle tests: the All Users group page, the invite dialog's link, a plain member and the settings, an unknown invitation code, creating, switching, renaming and deleting a workspace in the UI. The 3.0.0 client has no working page for workspace roles or for removing a member (the members page is not routed), so those stay API-only; the README records this as observation O-16. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
Ten lifecycle tests on the group pages: create, rename (an empty name refused), delete, add members, group roles, remove, exit (the only group admin cannot), the built-in groups and the developers group. Two are quarantined: a deleted group leaves its members the access it granted (D-53) and the API renames the all-users group (D-52). Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
…le suite Six lifecycle tests: the owner adds a member as viewer in the editor's share dialog, changes the role to editor, removes the row, toggles the public switch, a non-owner editor gets no Publish button, and the data source's Access Control grants and removes Can Use. Folders and bundles have no share UI in the 3.0.0 client and stay API-only. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
…ifecycle suite The echo sidecar now also accepts SMTP, so the mails the server sends (password reset, invitation) can be read back by recipient. A mailbox fixture reads them with Node's fetch, not a request context, so no token lands in a trace. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
…uite The forgot and reset pages, the token rules, the answer that hides whether an address has an account, and the invitation mail from the invite dialog. Seven tests that assert the desired behaviour are quarantined with new defect rows (sessions kept after a reset, the workspace template, an account in no workspace, a display name used as a reset address, the double-slash reset link, a raw translation key in the invite dialog, an outsider's invitation mail). Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
…suite What a removal or a leave does to a user's groups, app grants and apps, that the account survives in SAAS mode, and what deleting a workspace does to its members, groups, apps and invitations. Two tests that assert the desired behaviour are quarantined (a removed developer's data source grant and a removed member's folder grant both survive). Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
An admin adds, disables and deletes a GitHub provider in the UI, the workspace's sign-in page follows, the last sign-in method cannot be switched off, and the Generic form requires its issuer. A second configuration of one provider type is accepted by the server; that test is quarantined. Switching e-mail sign-in off is not tested: it ends the instance super admin's session, which the run shares. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
… lifecycle suite The echo sidecar can now serve canned answers per path prefix, so a Generic OAuth provider can be configured with its token and user-info endpoints on the test's own echo target. A first provider sign-in creates the user, the same user signs in again as the same account, registration off and a token error refuse the sign-in, and a provider user can bind an e-mail in the profile. A provider user whose address belongs to a form user is signed in as that user; that test is quarantined. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
… suite Adds a third stack profile, signup-disabled, and the tests LC-AU20 to LC-AU24: a refused sign-up, the register and sign-in pages, an invitation page and an admin's create-user call. Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
…mber detail and admin sign-in in the lifecycle suite Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
ludomikula
force-pushed
the
e2e-playwright-tests
branch
from
November 22, 2026 14:25
186a351 to
749922c
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Proposed changes
End to end tests against a running all-in-one container.
Types of changes
What types of changes does your code introduce to Lowcoder?
Put an
xin the boxes that apply.Checklist
You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put an
xin the boxes that apply.Further comments
n/a