test(sdk-core): Fix flaky test failures in FileAsyncResponseTransformerPublisherTest

[joviegas]

Use Flowable.just instead of hand-written mock publisher in FileAsyncResponseTransformerPublisherTest to prevent flaky test failures

Motivation and Context

Test FileAsyncResponseTransformerPublisherTest.requestManyTransformers_withResponseContainingDifferentContentRanges_shouldWriteToFileAtThoseRanges was flaky. It failed intermittently with "Expected size: 80 but was: 90" because some bytes were written to the file twice.

The possible root cause was the hand-written mock publisher used in the test. It emitted its data and called onComplete every time request(n) was called. FileSubscriber requests the next element after each write, so when the async file write finished before onComplete was processed, FileSubscriber requested again and the mock delivered the same bytes a second time. This is a race between the write completion and onComplete, which is why it only failed intermittently.

Modifications

Replaced the hand-written mock publisher with a spec-conformant publisher, SdkPublisher.adapt(Flowable.just(...)), which emits the data exactly once and does not re-emit on later requests. This is the same pattern already used in FileAsyncResponseTransformerTest (its testPublisher helper) for the same FileSubscriber write path. Updated both helpers in the test, createMockPublisherWithData and createMockPublisher.

License

• I confirm that this pull request can be released under the Apache 2 license

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.