Summary

The ADL test case "A successful find event with getMore" in getMore.json sets a "batchSize" of 3, then asserts that the getMore sends a "batchSize" of 1 (see here). It seems like it's based on an existing bug that was previously ignored by the spec test runner, but then was persisted when the spec test was converted to a unified spec test.

At least one other driver appears to have modified the spec test to correct the bug when copying into their own repo (see the Java version of the same spec test file here).

Motivation

Who is the affected end user?

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Yes.

Acceptance Criteria

Update batchSize: 1 to batchSize: 3 in "A successful find event with getMore" ADL spec test.