Disable Sentry in tests#159
Open
mendral-app[bot] wants to merge 1 commit into
Open
Conversation
Add _is_test_environment() guard in init_sentry() that checks for PYTEST_CURRENT_TEST env var or pytest in sys.modules. This prevents test runs from reporting mock-derived exceptions to the production Sentry project.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_is_test_environment()guard ininit_sentry()that detects pytest execution (viaPYTEST_CURRENT_TESTenv var orpytestinsys.modules) and skips Sentry initialization entirelyResolves: Test errors leaking to Sentry production
Note
Created by Mendral. Tag @mendral-app with feedback or questions.