Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core tests fail when run separately #37467

Closed
wants to merge 2 commits into from
Closed

Conversation

drajguru
Copy link
Contributor

Add orm mocking to settings test

Prevent putting the session into a state that prevents subsequent test modules from passing.
closes: #37466

@drajguru drajguru changed the title Core tests fail when run separately #37466 Core tests fail when run separately Feb 15, 2024
Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed in the issue, likely the assesment was based on the previous version of the test, that indeed monkeypached SQL_ALCHEMY_SETTINGS permanently for the rest of Pytest session and initalized other settings components as side-effect. - but #37320 just few days ago fixed exactly this problem.

The issue mentioned in the issue description does not seem to occur any more.

Requesting changes until it's clarified by the author.

@drajguru drajguru closed this Feb 16, 2024
@drajguru drajguru deleted the settings_sql branch February 16, 2024 03:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Core tests fail when run separately
2 participants