Skip to content

Decrease integration tests duration #1095

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
merged 2 commits into from
Jun 14, 2023
Merged

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Jun 13, 2023

80% of the integration tests was related to random temporal types tests.
Decrease the number of random test speeds up the process.

This is not a issue since these tests paths are already cover by property tests in the bolt-connection unit tests suite and in Testkit.

80% of the integration tests was related to random temporal types tests.
Make this tests run in parallel by starting all of them using `setImmediate` function.

Since `setImmediate` is not available in browsers, this tests will be skipped on this environment.
This is not a issue since these tests paths are already cover by property tests in the `bolt-connection` unit tests suite
and in Testkit.
80% of the integration tests was related to random temporal types tests.
Decrease the number of random test speeds up the process.

This is not a issue since these tests paths are already cover by property tests in the bolt-connection unit tests suite and in Testkit.
@bigmontz bigmontz merged commit 5185237 into neo4j:5.0 Jun 14, 2023
@bigmontz bigmontz deleted the speeding-up-tests branch June 14, 2023 11:48
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