Skip to content

Remove remaining stub tests and dependency on legacy stub server #1088

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
Nov 22, 2021

Conversation

injectives
Copy link
Contributor

@injectives injectives commented Nov 22, 2021

Reactive Testkit backend enabled a lot of Testkit tests to run on reactive driver. This update removes dependency on legacy stub server that is no longer maintained.

The remaining stub tests have been removed since there are similar tests in Testkit already, the tests and their respective Testkit alternatives are provided below:

  • DirectDriverBoltKitIT.shouldStreamingRecordsInBatchesRx -> TestIterationSessionRun.test_half_batch - Both test result consumption in batches.
  • DirectDriverBoltKitIT.shouldDiscardIfPullNotFinished -> TestIterationSessionRun.test_discards_on_session_close - Unlike the original, Testkit test consumes one record and discards the rest using session run intead of tx function. Based on its name, the original test purpose was to check if discard happens when result stream is not consumed in full and the suggested test covers this.
  • RoutingDriverBoltKitIT.shouldHandleLeaderSwitchAndRetryWhenWritingInTxFunctionRX -> RoutingV4x4.test_should_write_successfully_on_leader_switch_using_tx_function - Both check leader failure handling.

One of examples that dependended on stub server has been brought in line with the rest of examples and uses DatabaseExtension to manage server.

@injectives injectives force-pushed the feature/stubt branch 5 times, most recently from 396c929 to 72999de Compare November 22, 2021 14:13
@injectives injectives requested a review from gjmwoods November 22, 2021 14:13
Reactive Testkit backend enabled a lot of Testkit tests to run on reactive driver. This update removes dependency on legacy stub server that is no longer maintained.

The remaining stub tests have been removed since there are similar tests in Testkit already, the tests and their respective Testkit alternatives are provided below:
- `DirectDriverBoltKitIT.shouldStreamingRecordsInBatchesRx` -> `TestIterationSessionRun.test_half_batch` - Both test result consumption in batches.
- `DirectDriverBoltKitIT.shouldDiscardIfPullNotFinished` -> `TestIterationSessionRun.test_discards_on_session_close` - Unlike the original, Testkit test consumes one record and discards the rest using session `run` intead of tx function. Based on its name, the original test purpose was to check if discard happens when result stream is not consumed in full and the suggested test covers this.
- `RoutingDriverBoltKitIT.shouldHandleLeaderSwitchAndRetryWhenWritingInTxFunctionRX` -> `RoutingV4x4.test_should_write_successfully_on_leader_switch_using_tx_function` - Both check leader failure handling.

One of examples that dependended on stub server has been brought in line with the rest of examples and uses `DatabaseExtension` to manage server.
Copy link
Contributor

@gjmwoods gjmwoods left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@injectives injectives merged commit 3fad057 into neo4j:4.4 Nov 22, 2021
@injectives injectives deleted the feature/stubt branch November 22, 2021 20:57
injectives added a commit to injectives/neo4j-java-driver that referenced this pull request Jan 31, 2022
…4j#1088)

* Remove remaining stub tests and dependency on legacy stub server

Reactive Testkit backend enabled a lot of Testkit tests to run on reactive driver. This update removes dependency on legacy stub server that is no longer maintained.

The remaining stub tests have been removed since there are similar tests in Testkit already, the tests and their respective Testkit alternatives are provided below:
- `DirectDriverBoltKitIT.shouldStreamingRecordsInBatchesRx` -> `TestIterationSessionRun.test_half_batch` - Both test result consumption in batches.
- `DirectDriverBoltKitIT.shouldDiscardIfPullNotFinished` -> `TestIterationSessionRun.test_discards_on_session_close` - Unlike the original, Testkit test consumes one record and discards the rest using session `run` intead of tx function. Based on its name, the original test purpose was to check if discard happens when result stream is not consumed in full and the suggested test covers this.
- `RoutingDriverBoltKitIT.shouldHandleLeaderSwitchAndRetryWhenWritingInTxFunctionRX` -> `RoutingV4x4.test_should_write_successfully_on_leader_switch_using_tx_function` - Both check leader failure handling.

One of examples that dependended on stub server has been brought in line with the rest of examples and uses `DatabaseExtension` to manage server.

* Renamed RoutingDriverBoltKitIT to ResolverIT
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