[JAVA-5124] Ensure retryable writes tests execute on non-replica sets Created: 29/Aug/23 Updated: 28/Oct/23 Resolved: 31/Aug/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Retryability, Test Coverage |
| Affects Version/s: | None |
| Fix Version/s: | 4.11.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Documentation Changes: | Not Needed | ||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||
| Description |
|
In the legacy (non-unified) retryable writes test suite, there is a faulty check in com.mongodb.client.AbstractRetryableWritesTest#data that causes the tests to be skipped if the cluster is not a replica set, which means the tests don't run on sharded or serverless clusters. The faulty check should be removed. |
| Comments |
| Comment by Githook User [ 31/Aug/23 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Remove incorrect test-skipping logic (#1186) Skip newly-running but failing tests in code
|