You can create a PipelineOption which represents your Redis client object. For tests you would set the PipelineOption to a serializable fake/mock that can replay the results you want. The default for the PipelineOption object would instantiate your production client. You can see an example usage of the DefaultValueFactory here[1].
1: https://github.com/apache/beam/blob/5cebe0fd82ade3f957fe70e25aa3e399d2e91b32/runners/direct-java/src/main/java/org/apache/beam/runners/direct/DirectOptions.java#L71 On Mon, Jun 14, 2021 at 10:54 AM gaurav mishra <[email protected]> wrote: > Hi, > I have a streaming pipeline which reads from pubsub, enriches data using > redis and finally writes to pubsub. The code has some stateful DoFns with > timers. I wanted to write unit tests for the whole pipeline, that reads > from TestStream<> , enriches data using a mocked redis client, and writes > data to a PCollection on which I can do PAsserts. The trouble I am having > here is how to set up the mocked redis client. Are there any examples that > I can take a look at? I am using java with junit4 as a testing framework. > More details about my code are here - > https://stackoverflow.com/questions/67963189/unit-tests-apache-beam-stateful-pipeline-with-external-dependencies >
