Skip to content

Conversation

@ArtemHoruzhenko
Copy link
Contributor

@ArtemHoruzhenko ArtemHoruzhenko commented Dec 1, 2025

What

Web E2E tests fixes
Temporary added possibility to trigger this tests by pushing to e2e/** branch

Testing

Technical task. Nothing to test here


Note

Updates E2E tests to align with new UI selectors/behavior (incl. Pub/Sub pagination/status and forcing list view), adds testids in Pub/Sub UI, and enables CI workflow on e2e/** pushes.

  • E2E Tests:
    • Update selectors and expectations across Browser, Pub/Sub, CLI Helper, Navigation, Streams, and Overview (e.g., pub-sub-status, pub-sub-messages-count, publish-result, confirm-popover, header <p>, keys "No results" container).
    • Force switch to list view in multiple fixtures via browserViewButton to stabilize tests.
    • Pub/Sub: adjust status checks to Subscribed/Unsubscribed, use messages table/pagination controls, and verify publish result badge; mark some debug/clear tests as skipped.
    • Browser: refine filtering, scanning, and tooltip text checks; add keysContainer selector; tweak sorting/labels and stream table assertions.
  • UI (Pub/Sub):
    • Add data-testid hooks in MessagesListTable (messages count, status) and PublishMessage (publish result).
  • CI/CD:
    • Enable E2E workflow to run on push to e2e/** branches.

Written by Cursor Bugbot for commit ea59cc1. This will update automatically on new commits. Configure here.

@@ -1,6 +1,9 @@
name: ✅ E2E Tests
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: Since we already have variations of labels that trigger the different types of tests, you can also extend them with one more, targeting the e2e tests 🙂

Image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure. we will do it eventually

await t.click(pubSubPage.messagesTableFirstPageBtn);

// ...
})
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Incomplete placeholder test committed to codebase

A test named 'Example of new test' was added that appears to be incomplete placeholder code. The generic name suggests it's a template or work-in-progress, and the test body ends with a // ... comment indicating it's unfinished. While the entire fixture is currently skipped, this placeholder test introduces noise to the codebase and may cause confusion or be accidentally enabled later.

Fix in Cursor Fix in Web

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.

3 participants