damccorm opened a new issue, #20572: URL: https://github.com/apache/beam/issues/20572
:test tasks should generally just run unit tests or fast running tests that use an in-memory (or containerized) fake, but it can be tempting to write simple tests that leverage production cloud services, and not classify them as integration tests (e.g. BEAM-11363). We should have some automation to protect against this - we can run :test tasks in a hermetic environment in precommits. One possible approach: use a docker container with networking disable (maybe re-use the Beam developer container BEAM-10891) Imported from Jira [BEAM-11404](https://issues.apache.org/jira/browse/BEAM-11404). Original Jira may contain additional context. Reported by: bhulette. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
