Skip to content

Conversation

0xbad0c0d3
Copy link
Contributor

I was running tests locally and noticed that they are stays running if something wents wrong that's why I've added: 04d2fbf

fixes #17514

Is there a way to run e2e tests pipeline without merging to develop?

cod1k added 2 commits September 25, 2025 09:45
Updated test definitions across multiple suites to accept and pass abort signals (`signal`) for enhanced request handling. Adjusted the `start` method in the test runner to support optional abort signals.
Reworked `copyExecutionContext` to use a dynamic property descriptor approach, enabling method overrides without altering the original object. Expanded test cases to cover additional methods and verify override behavior.
cursor[bot]

This comment was marked as outdated.

Enhanced the descriptor logic to better handle non-function properties and prevent invalid method overrides. Fixed potential issues with binding non-function properties to the context.
cursor[bot]

This comment was marked as outdated.

cod1k added 2 commits September 26, 2025 08:52
Updated the `OverridesStore` type to strictly associate keys with context-specific methods, improving type safety. Renamed and enhanced the descriptor creation function to better handle method overriding and added checks for function-only properties.
@mydea
Copy link
Member

mydea commented Sep 26, 2025

You should be able to run E2E tests locally:

cd dev-packages/e2e-tests
yarn test:run test-app-name

This requires docker & pnpm to be setup!

@andreiborza
Copy link
Member

@0xbad0c0d3 is this ready for review?

@0xbad0c0d3
Copy link
Contributor Author

No, not yet, sorry for the delay.

@andreiborza
Copy link
Member

No worries, just wasn't sure :) When you're ready, please request me as a reviewer.

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.

@sentry/cloudflare crashes DurableObjects due to unsafe & unnecessary proxying of waitUntil()
3 participants