Skip to content

Conversation

@injectives
Copy link
Contributor

No description provided.

@injectives injectives requested a review from robsdedude August 11, 2021 09:53
Copy link
Contributor

@robsdedude robsdedude left a comment

Choose a reason for hiding this comment

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

Makes sense, as there is no fetch size in v3.

@injectives injectives merged commit ce03a6b into neo4j-drivers:4.4 Aug 11, 2021
@injectives injectives deleted the feature/skip branch August 11, 2021 10:57
injectives added a commit to injectives/testkit that referenced this pull request Aug 11, 2021
injectives added a commit that referenced this pull request Aug 11, 2021
* Migrate tests from java driver (#206)

* Migrate tests from java driver

This updated also includes:
- TransactionClose request support (`Temporary:TransactionClose` feature)
- Driver fetch size configuration (`Temporary:DriverFetchSize` feature)

Migrated tests:
- shouldThrowRollbackErrorWhenTransactionRollback -> test_should_error_on_rollback_failure_using_tx_rollback
- shouldThrowRollbackErrorWhenTransactionClose -> test_should_error_on_rollback_failure_using_tx_close
- shouldPropagateTransactionRollbackErrorWhenSessionClosed -> test_should_error_on_rollback_failure_using_session_close
- shouldStreamingRecordsInBatches -> test_should_accept_custom_fetch_size_using_driver_configuration (protocol bump from 4 to 4.1)
- shouldChangeFetchSize -> test_should_accept_custom_fetch_size_using_session_configuration (protocol bump from 4 to 4.1)

* Update TMP_DRIVER_FETCH_SIZE feature comment

* Update _assert_is_transient_exception check for java driver

* Remove pipelining from direct scripts and update fetchSize handling

* Add optional RESET to writer_with_custom_fetch_size.script

* Skip direct rollback tests for go and javascript

* Skip direct rollback test for javascript

* Skip test_should_error_on_rollback_failure_using_session_close for dotnet

* Skip test_should_accept_custom_fetch_size_using_driver_configuration in v3 (#210)
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