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

Migrate Java IT tests to Testkit #1097

Merged
merged 1 commit into from
Dec 7, 2021
Merged

Conversation

injectives
Copy link
Contributor

@injectives injectives commented Dec 6, 2021

Migrated tests:

  • CausalClusteringIT.shouldNotReuseReadConnectionForWriteTransaction -> TestBookmarks.test_does_not_use_read_connection_for_write
  • CausalClusteringIT.shouldExecuteReadAndWritesWhenDriverSuppliedWithAddressOfLeader -> Routing.test_should_get_rt_from_leader_w_and_r_via_leader_using_session_run
  • CausalClusteringIT.shouldExecuteReadAndWritesWhenDriverSuppliedWithAddressOfFollower -> Routing.test_should_get_rt_from_follower_w_and_r_via_leader_using_session_run
  • CausalClusteringIT.shouldDropBrokenOldConnections -> Routing.test_should_drop_connections_failing_liveness_check
  • CausalClusteringIT.shouldRespectMaxConnectionPoolSizePerClusterMember -> Routing.test_should_enforce_pool_size_per_cluster_member
  • CausalClusteringIT.shouldKeepOperatingWhenConnectionsBreak -> unexpected interruptions are covered by routing tests Routing.test_should_retry_read_tx_until_success_on_run_error, Routing.test_should_retry_read_tx_until_success_on_pull_error, Routing.test_should_retry_read_tx_until_success_on_error, Routing.test_should_retry_read_tx_and_rediscovery_until_success_on_run_failure, Routing.test_should_retry_read_tx_and_rediscovery_until_success_on_pull_failure, Routing.test_should_retry_read_tx_and_rediscovery_until_success, Routing.test_should_retry_write_tx_and_rediscovery_until_success_on_run_failure, Routing.test_should_retry_write_until_success_with_leader_change_on_run_using_tx_function, Routing.test_should_retry_write_tx_until_success_on_run_error, Routing.test_should_retry_write_tx_until_success_on_pull_error, Routing.test_should_retry_write_tx_and_rediscovery_until_success_on_pull_failure, Routing.test_should_retry_write_until_success_with_leader_change_using_tx_function, Routing.test_should_retry_write_tx_until_success_on_error, Routing.test_should_retry_write_tx_and_rediscovery_until_success

Converted tests:

  • CausalClusteringIT.shouldExecuteReadAndWritesWhenRouterIsDiscovered -> GraphDatabaseTest.shouldNotFailRoutingDriverWhenThereIsWorkingUri

New Testkit features:

  • Feature:API:Liveness.Check
  • Temporary:DriverMaxConnectionPoolSize
  • Temporary:ConnectionAcquisitionTimeout
  • Temporary:GetConnectionPoolMetrics

The address field has been added to Summary Testkit response.

@injectives injectives requested a review from gjmwoods December 6, 2021 18:34
Migrated tests:
- `CausalClusteringIT.shouldNotReuseReadConnectionForWriteTransaction` -> `TestBookmarks.test_does_not_use_read_connection_for_write`
- `CausalClusteringIT.shouldExecuteReadAndWritesWhenDriverSuppliedWithAddressOfLeader` -> `Routing.test_should_get_rt_from_leader_w_and_r_via_leader_using_session_run`
- `CausalClusteringIT.shouldExecuteReadAndWritesWhenDriverSuppliedWithAddressOfFollower` -> `Routing.test_should_get_rt_from_follower_w_and_r_via_leader_using_session_run`
- `CausalClusteringIT.shouldDropBrokenOldConnections` -> `Routing.test_should_drop_connections_failing_liveness_check`
- `CausalClusteringIT.shouldRespectMaxConnectionPoolSizePerClusterMember` -> `Routing.test_should_enforce_pool_size_per_cluster_member`
- `CausalClusteringIT.shouldKeepOperatingWhenConnectionsBreak` -> unexpected interruptions are covered by routing tests `Routing.test_should_retry_read_tx_until_success_on_run_error`, `Routing.test_should_retry_read_tx_until_success_on_pull_error`, `Routing.test_should_retry_read_tx_until_success_on_error`, `Routing.test_should_retry_read_tx_and_rediscovery_until_success_on_run_failure`, `Routing.test_should_retry_read_tx_and_rediscovery_until_success_on_pull_failure`, `Routing.test_should_retry_read_tx_and_rediscovery_until_success`, `Routing.test_should_retry_write_tx_and_rediscovery_until_success_on_run_failure`, `Routing.test_should_retry_write_until_success_with_leader_change_on_run_using_tx_function`, `Routing.test_should_retry_write_tx_until_success_on_run_error`, `Routing.test_should_retry_write_tx_until_success_on_pull_error`, `Routing.test_should_retry_write_tx_and_rediscovery_until_success_on_pull_failure`, `Routing.test_should_retry_write_until_success_with_leader_change_using_tx_function`, `Routing.test_should_retry_write_tx_until_success_on_error`, `Routing.test_should_retry_write_tx_and_rediscovery_until_success`

Converted tests:
- `CausalClusteringIT.shouldExecuteReadAndWritesWhenRouterIsDiscovered` -> `GraphDatabaseTest.shouldNotFailRoutingDriverWhenThereIsWorkingUri`

New Testkit features:
- `Feature:API:Liveness.Check`
- `Temporary:DriverMaxConnectionPoolSize`
- `Temporary:ConnectionAcquisitionTimeout`
- `Temporary:GetConnectionPoolMetrics`

The `address` field has been added to `Summary` Testkit response.
@injectives injectives merged commit 2d2f375 into neo4j:4.4 Dec 7, 2021
@injectives injectives deleted the feature/testmig branch December 7, 2021 16:06
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