Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP TestCafe tests are flaky/failing #414

Closed
wants to merge 43 commits into from

Conversation

pauldambra
Copy link
Member

@pauldambra pauldambra commented Jun 24, 2022

Changes

TestCafe tests wait for three events to have been received by PostHog

They consistently fail without receiving all three. But are not consistent with which of the three they don't receive.

They are also not consistent with which browser fails.

Checklist

  • Tests for new code (see advice on the tests we use)
  • Accounted for the impact of any changes across different browsers
  • TypeScript definitions (module.d.ts) updated and in sync with library exports (if applicable)

@posthog-bot
Copy link
Collaborator

Hey @pauldambra! 👋
This pull request seems to contain no description. Please add useful context, rationale, and/or any other information that will help make sense of this change now and in the distant Mars-based future.

@pauldambra pauldambra changed the title WIP DO NOT MERGE - just want to run tests on master WIP TestCafe tests are flaky/failing Jun 24, 2022
@pauldambra
Copy link
Member Author

pauldambra commented Jun 24, 2022

run test browser events
1 custom events chrome custom-event, $pageview
2 autocaptured events chrome $autocapture, $pageview
3 config options chome $autocapture, $pageview
4 autocaptured events chrome $autocapture, $pageview
5 autocaptured events safari $autocapture, $pageview
6 custom events chrome $pageview, custom-event
7 custom events chrome $pageview, custom-event
8 custom events chrome $pageview, custom-event

run 7 and 8 logged

Browser log: sent custom event
Browser warn: Enqueued failed request for retry in 6000
Browser warn: Enqueued failed request for retry in 6000
Browser error: Bad HTTP status: 0
Browser error: Bad HTTP status: 0

README.md Outdated Show resolved Hide resolved
@pauldambra pauldambra force-pushed the chore/does-test-cafe-fail-for-master branch from 91f6dcd to ca4f566 Compare July 22, 2022 21:33
@pauldambra
Copy link
Member Author

superseded by #428

@pauldambra pauldambra closed this Jul 26, 2022
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