Skip to content

Fix flaky tests on TransactionExecutor suite #1137

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

Merged

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Sep 6, 2023

The TransactionExecutor tests were mocking the global setTimeout and clearTimeout. This mocks were conflicting with other calls to this api in the browser tests. So, the calls to the set/clear were not being the expected in some situations.

Replace the global mock for injecting the functions resolve this issue in a less intrusive way.

The TransactionExecutor tests were mocking the global setTimeout and clearTimeout.
This mocks were conflicting with other calls to this api in the browser tests.
So, the calls to the set/clear were not being the expected in some situations.

Replace the global mock for injecting the functions resolve this issue in a less intrusive way.
@bigmontz bigmontz force-pushed the 5.13-fix-flacky-on-transaction-executor-tests branch from 13f1d3b to 3b3827c Compare September 6, 2023 10:27
@bigmontz bigmontz merged commit cf1fde8 into neo4j:5.0 Sep 7, 2023
@bigmontz bigmontz deleted the 5.13-fix-flacky-on-transaction-executor-tests branch September 7, 2023 12:27
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