Thank you and I filed https://issues.apache.org/jira/browse/BEAM-12682 to track this. (/cc @David Huntsperger <dhuntsper...@google.com> )
Related question to everyone, do we have a process for the "Beam Website Feedback" emails? I see these emails occasionally, and some of them are for trivial issues and addressed quickly but some are like this one and require more work. I guess our current approach of assessing case by case is also working reasonably well. On Fri, Jul 23, 2021 at 5:17 PM Falak Singhal <falak.sing...@samsclub.com> wrote: > Feedback for documentation on Testing Beam pipeline > > > > The documentation is not at all detailed and is pretty shallow, hardly > covering most concepts to effectively design test-suit for an enterprise > level pipeline. > > > > For example, some the missing information are – > > 1. How to test the pipeline when the PTransform outputs tuple tags > 2. How to design a negative test case where PTransform throws an > exception > 3. How to examine the data of the PCollection in PAssert. Something > better than containsInAnyOrder is required. > > > > Please note that the list is not exhaustive! > > > > URL - > > https://beam.apache.org/documentation/pipelines/test-your-pipeline/ > > > > Best, > > Falak >
