kennknowles edited a comment on pull request #14504: URL: https://github.com/apache/beam/pull/14504#issuecomment-819121637
One thing I'd like to get from the `ValidatesRunner` table is that it primarily validates the runner properly implements the basic primitives. Mostly, the different languages are redundant, except when it comes to specialized optimizations. The ULR "ValidatesRunner" column would ideally validate that the SDK harness properly implements the Fn API primitives. I don't think we can quite avoid having the full matrix, but it might be able to be more sparse without losing coverage, or at least be easy to quickly read off what the trouble is. Trying to avoid "testing nihilism" in which the only definition of correctness is the whole system passing integration tests together. This gets really expensive to run and debug and in my experience tests end up living a long time without owners because eventually no one knows exactly what it is testing or whether it is safe to ignore. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
